-
Notifications
You must be signed in to change notification settings - Fork 579
OCPNODE-3187: Promote SigstoreVerificatoin to Default #2340
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
OCPNODE-3187: Promote SigstoreVerificatoin to Default #2340
Conversation
|
Skipping CI for Draft Pull Request. |
|
Hello @QiWang19! Some important instructions when contributing to openshift/api: |
|
/test verify-feature-promotion |
|
/test e2e-aws-ovn-techpreview-serial |
|
@QiWang19: The specified target(s) for The following commands are available to trigger optional jobs: 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. |
|
/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial |
|
@QiWang19: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ee5d5840-3733-11f0-9df1-5c867339a323-0 |
|
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview |
|
@QiWang19: The specified target(s) for The following commands are available to trigger optional jobs: 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 e2e-aws-serial-techpreview-1of2 /test e2e-aws-serial-techpreview-2of2 /test e2e-aws-ovn-techpreview |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
4 similar comments
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
@QiWang19: This pull request references OCPNODE-3187 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
8d721a1 to
227dcf7
Compare
|
/test verify-feature-promotion |
1 similar comment
|
/test verify-feature-promotion |
|
@QiWang19 At the moment there appears to be no metal or SNO testing for this feature, is it not applicable to those platforms? |
Signed-off-by: Qi Wang <[email protected]>
227dcf7 to
bc9a3d5
Compare
|
@JoelSpeed I rebased. The test result now shows it runs on SNO |
|
@QiWang19 Yep, can see all of those tests now, you're down on runs per the requirements so it looks like you'll have to use Have you used gangway before for this purpose? |
|
@JoelSpeed I did not know that we can use I triggered some tests, will |
Yep, the verify includes any tests that report into component readiness. So provided the job you triggered already reports into component readiness, this would count towards the verify |
|
/test verify-feature-promotion |
|
@QiWang19 You can see that the AWS result is now showing 22 runs which includes the 14 you triggered |
|
/test verify-feature-promotion |
|
regarding the result of
I worked with MCO team help take a look at the aws single-node test failure, it is caused by flawed test logic (a false-positive in pool-completion checks), not the feature itself. PR openshift/origin#30115 proposed to fix the test's waiting logic. I think this is a test infrastructure problem, not a regression in the actual feature. GA isn’t blocked by this test bugs.
On metal CI only runs IPv4 since mirroring Sigstore attachments for IPv6 is unsupported by ci right now. QE has manually verified IPv6 disconnected environments
will trigger more test runs on metal with IPv4. (https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2340/pull-ci-openshift-api-master-verify-feature-promotion/1956354241832423424) |
|
/test verify-feature-promotion |
2 similar comments
|
/test verify-feature-promotion |
|
/test verify-feature-promotion |
|
/lgtm This feature does not work with our ipv6/dual stack based CI environements, so we are ignoring those columns The only failing block on the grid otherwise is a single SNO test, which has been fixed in openshift/origin#30115 and since has passed 37 times in a row, we are confident that this would go green naturally but adding the LGTM now to give a bit more breathing space before the branch date |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-feature-promotion 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed, QiWang19 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@QiWang19: The following tests 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. |
2d02a45
into
openshift:master
|
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-config-api |
No description provided.