Tag for build #347342 is 3.69.x-138-gb3a54d2942.

💻 For deploying this image using the dev scripts, run the following first:

export MAIN_IMAGE_TAG='3.69.x-138-gb3a54d2942'

📦 You can also generate an installation bundle with:

docker run -i --rm stackrox/main:3.69.x-138-gb3a54d2942 central generate interactive > bundle.zip

🕹️ A roxctl binary artifact can be downloaded from CircleCI.

Not sure if it's a flake, but maybe the failing nongroovy test is due to missing dependency package

=== CONT  TestCASetup/https://untrusted-root.badssl.com
    ca_setup_test.go:82: 
        	Error Trace:	ca_setup_test.go:82
        	Error:      	Not equal: 
        	            	expected: 4
        	            	actual  : 1
        	Test:       	TestCASetup/https://untrusted-root.badssl.com
        	Messages:   	received resp: result:CERT_SIGNED_BY_UNKNOWN_AUTHORITY details:"Get \"https://untrusted-root.badssl.com\": x509: certificate signed by unknown authority" . This failure likely means that setting up trusted CAs with Central is broken. Look at the TRUSTED_CA_FILE being exported in the deploy scripts

I think we're quite lucky that it's just one failing test.

Check out our downstream Dockerfile https://code.engineering.redhat.com/gerrit/gitweb?p=rhacs.git;a=blob_plain;f=distgit/containers/rhacs-main/Dockerfile.in;hb=refs/heads/rhacs-1.0-rhel-8

It might be one packages in this command microdnf install -y ca-certificates findutils snappy zstd that would make us happy.

Not sure if it's a flake, but maybe the failing nongroovy test is due to missing dependency package

Not a flake, but apparently 3rd party certificate expiration. We saw that before: chromium/badssl.com#477

3rd party certificate expiration

I don't think it is that. The cert for https://untrusted-root.badssl.com/ is valid till Sat, 10 Feb 2024 02:30:33 GMT and CA is valid till Wed, 02 Jul 2036 06:31:35 GMT.
The test has failed where it was supposed to pass. The failure message says:

x509: certificate signed by unknown authority [...] This failure likely means that setting up trusted CAs with Central is broken.

Central was supposed to install CA for https://untrusted-root.badssl.com/ and the connection was expected to succeed.
I think that ca-certificates package adds tools allowing to install thirdparty CAs.

Closing in favor of #1054.