-
Notifications
You must be signed in to change notification settings - Fork 698
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
Add OCP and RHCOS assertion files for 4.17 #12266
Add OCP and RHCOS assertion files for 4.17 #12266
Conversation
This will make it so we can get clean periodic CI runs using the latest version of OCP.
/test |
@rhmdnd: The
Use
In 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 4.17-e2e-aws-ocp4-bsi |
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
These rules are passing on 4.17, so let's update them so we assert passing status in subsuquent runs.
/test 4.17-e2e-aws-ocp4-pci-dss |
looks like the failure is from manual remediation for ingress cert |
/test 4.17-e2e-aws-ocp4-bsi |
4.17-e2e-aws-ocp4-e8 and 4.17-e2e-aws-ocp4-cis-node failed due to unrelated cluster install issues. 4.17-e2e-aws-ocp4-moderate failed on an e2e timeout we're addressing in #12268. 4.17-e2e-aws-rhcos4-moderate failed on the following assertions:
|
/test 4.17-e2e-aws-ocp4-moderate |
/test 4.17-e2e-aws-ocp4-stig-node |
@rhmdnd: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/test 4.17-e2e-aws-ocp4-moderate |
These rules were failing in the past because the networking operator created the file with permissions of 644. That's been tightened, so this rule is passing by default for 4.17: openshift/cluster-network-operator#2106
2bda2e0
to
ca60c1a
Compare
/test 4.17-e2e-aws-ocp4-moderate |
Code Climate has analyzed commit ca60c1a 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 59.4% (0.0% change). View more on Code Climate. |
@yuumasato should be ready for another look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great.
Restarted required CI that failed.
This will make it so we can get clean periodic CI runs using the latest
version of OCP.