-
Notifications
You must be signed in to change notification settings - Fork 138
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
OCPBUGS-23102: Revert #266 "OCPBUGS-21718: go.mod: bump golang.org/x/net to v0.17.0" #268
Conversation
@stbenjam: This pull request references Jira Issue OCPBUGS-23102, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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/test-infra repository. |
/hold |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stbenjam The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@stbenjam: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/78a5a300-7f01-11ee-9b57-8ae3bf59e63a-0 |
/close It was openshift/origin#28389 |
@stbenjam: This pull request references Jira Issue OCPBUGS-23102. The bug has been updated to no longer refer to the pull request using the external bug tracker. 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/test-infra repository. |
Reverts #266 ; tracked by OCPBUGS-23102
Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.
All metal jobs are broken and we don't have an obvious culprit, TRT is floating a few reverts for investigation.
To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:
CC: @s-urbaniak