Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Staled content image: quay.io/complianceascode/ocp4:latest #8495

Closed
Vincent056 opened this issue Apr 5, 2022 · 6 comments · Fixed by #8622
Closed

Staled content image: quay.io/complianceascode/ocp4:latest #8495

Vincent056 opened this issue Apr 5, 2022 · 6 comments · Fixed by #8622

Comments

@Vincent056
Copy link
Contributor

Vincent056 commented Apr 5, 2022

Description of problem:

The quay.io/complianceascode/ocp4:latest image seems stale, the last update to it was from two months ago. We use this image as our compliance operator upstream image as well as in our CI.

@Vincent056 Vincent056 changed the title Staled quay.io/complianceascode/ocp4:latest Staled content image: quay.io/complianceascode/ocp4:latest Apr 5, 2022
@Vincent056 Vincent056 changed the title Staled content image: quay.io/complianceascode/ocp4:latest Staled content image: quay.io/complianceascode/ocp4:latest Apr 5, 2022
@rhmdnd
Copy link
Collaborator

rhmdnd commented Apr 6, 2022

Thanks for filing the bug. Providing some additional context.

I'm getting the following error when I run the tests locally:

helpers.go:808: E2E-FAILURE: The expected result for the enable_fips_mode rule didn't match. Expected 'PASS', Got 'FAIL'
<snip>
=== RUN   TestE2e/We_should_have_the_same_number_of_check_results_in_each_scan
    e2e_test.go:130: There amount of check results are the same: init -> 472  end 472
=== RUN   TestE2e/We_should_have_less_failures
    e2e_test.go:140: There are less failures now: init -> 370  end 4
=== RUN   TestE2e/We_should_have_no_errors_or_invalid_results
--- FAIL: TestE2e (3457.01s)
    --- PASS: TestE2e/Parameter_setup_and_validation (3.68s)
    --- PASS: TestE2e/Operator_setup (40.96s)
    --- PASS: TestE2e/Prereqs_setup (68.80s)
    --- FAIL: TestE2e/Run_first_compliance_scan (232.81s)
    --- PASS: TestE2e/Wait_for_Remediations_to_apply (1130.61s)
    --- PASS: TestE2e/Apply_manual_remediations (3.41s)
    --- PASS: TestE2e/Wait_for_manual_Remediations_to_apply (761.38s)
    --- PASS: TestE2e/Check_for_remediations_with_dependencies_before_scan_2 (0.13s)
    --- PASS: TestE2e/Run_compliance_scan_#2 (128.98s)
    --- PASS: TestE2e/Scan_2:_Wait_for_Remediations_to_apply (870.85s)
    --- PASS: TestE2e/Check_for_remediations_with_dependencies_before_scan_3 (0.11s)
    --- FAIL: TestE2e/Run_compliance_scan_#3 (155.28s)
    --- PASS: TestE2e/We_should_have_the_same_number_of_check_results_in_each_scan (0.00s)
    --- PASS: TestE2e/We_should_have_less_failures (0.00s)
    --- PASS: TestE2e/We_should_have_no_errors_or_invalid_results (0.00s)
FAIL
FAIL    github.com/ComplianceAsCode/ocp4e2e     3457.026s
FAIL
make: *** [Makefile:20: e2e] Error 1

Which causes the scans to fail even though the issue was fixed upstream [0].

[0] #8348

@tmishina
Copy link
Contributor

Hi, I'd like to understand the status of this issue because I need to use the latest ocp4 content with Compliance Operator installed via OperatorHub, which automatically uses quay.io/complianceascode/ocp4:latest. Is there any plan to fix this? Thanks.

@rhmdnd
Copy link
Collaborator

rhmdnd commented Apr 13, 2022

We are planning to fix this and we're working on a solution to update the content. Hopefully we'll have something running this week.

@tmishina
Copy link
Contributor

Hi, is there any update on this issue? Although I can personally use self-built image, customers using public CO instances such as installed via OperatorHub rely on this public image.

@rhmdnd
Copy link
Collaborator

rhmdnd commented Apr 22, 2022

We have new content available here https://quay.io/repository/compliance-operator/compliance-operator-content

I'm in the process of updating references in compliance-operator and test repositories.

openshift/compliance-operator#821
ComplianceAsCode/ocp4e2e#27

@rhmdnd
Copy link
Collaborator

rhmdnd commented Apr 26, 2022

The CI against openshift/compliance-operator is running with the new content. @JAORMX has a patch to push additional content images to ghcr.io, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants