OCPBUGS-55140: Enhance RHCOS checks to include CoreOS variant for 4.19#13369
OCPBUGS-55140: Enhance RHCOS checks to include CoreOS variant for 4.19#13369rhmdnd merged 1 commit intoComplianceAsCode:masterfrom
Conversation
|
/test |
|
@Vincent056: The Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/test e2e-aws-rhcos4-high |
|
/test 4.19-e2e-aws-rhcos4-high |
|
@Vincent056 Seems it still returns NOT-APPLICABLE for upstream-rhcos4-moderate profile. Could you please help to check again? Thanks. |
Signed-off-by: Vincent Shen <wenshen@redhat.com>
|
Code Climate has analyzed commit 3327fa3 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 61.9% (0.0% change). View more on Code Climate. |
|
/test e2e-aws-rhcos4-high |
|
Verification pass with content built from PR #13369: |
|
@Vincent056: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
For 4.19-e2e-aws-rhcos4-high job: |
|
Seems to continue working on 4.16, which is good. |
rhmdnd
left a comment
There was a problem hiding this comment.
/lgtm
Nearly all the differences in the assertions between 4.19 and 4.18 are related to the ARM rules, where we set them to or NOT-APPLICABLE.
Otherwise, it looks like the majority of what's in the assertion file generated by the suite it the same as what is in the assertion file for 4.18.
On OCP 4.19+ we are using RHEL bootimages, we should include that to rhcos platform CPE.
Related Changes: openshift/installer#9392