Lance Bragstad
Lance Bragstad
We're seeing the following issue crop up consistently in CI: ``` 2024/07/22 19:38:13 waiting until suite test-scan-has-profile-g-u-i-d reaches target status 'DONE'. Current status: RUNNING 2024/07/22 19:38:18 waiting until suite test-scan-has-profile-g-u-i-d...
There appears to be a transient issue in the ROSA e2e tests that gives the following error: ``` 024/07/22 20:04:55 Waiting for full availability of compliance-operator deployment (0/1) 2024/07/22 20:05:00...
Last year we refactored the e2e test suite by separating parallel and serial tests into separate packages. https://github.com/ComplianceAsCode/compliance-operator/pull/264 This reduce the amount of custom test runner code we needed to...
The following ciphers are all supported with TLS v1.3, but we weren't checking for them in the OpenShift ingress controller configuration: - TLS_AES_128_GCM_SHA256 - TLS_AES_256_GCM_SHA384 - TLS_CHACHA20_POLY1305_SHA256 This commit updates...
We've been seeing the following error in our e2e testing: ``` 2024/09/03 18:51:39 deleting ClusterRole profilebundle-editor-role 2024/09/03 18:51:40 deleting ClusterRole profilebundle-viewer-role 2024/09/03 18:51:40 deleting ClusterRole remediation-aggregator 2024/09/03 18:51:40 deleting ClusterRole...
We need to remove annotations when rerunning a scan, regardless of it being rerun for a timeout or a rescan. We handled these cases separately, but didn't need to since...
This commit enables power and Z builds for the operator, openscap, and must-gather images. Subsequent patches will enable it for the bundle build, which needs to enable hermetic builds, too.