-
Notifications
You must be signed in to change notification settings - Fork 328
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-44960: (OSASINFRA-3643) bump k8s and dependencies #4927
base: main
Are you sure you want to change the base?
Conversation
@EmilienM: This pull request explicitly references no jira issue. 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. |
@EmilienM: This pull request references Jira Issue OCPBUGS-43459, 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@EmilienM: This pull request references Jira Issue OCPBUGS-43459, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request. 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. |
@EmilienM: This pull request references Jira Issue OCPBUGS-43459, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (emacchi@redhat.com), skipping review request. 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. |
8b71b0b
to
41be629
Compare
/hold |
/hold cancel |
/test e2e-aws |
@@ -29,7 +29,7 @@ spec: | |||
metadata: | |||
annotations: | |||
cluster-autoscaler.kubernetes.io/safe-to-evict-local-volumes: work-logs | |||
component.hypershift.openshift.io/config-hash: 19dc307e3415eb66 |
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.
Why is this changing? does this mean this would cause a fleet wide rollout of this components?
I'll squash the third commit into the first if that passes verify and unit jobs. |
/test e2e-aws |
/retest-required |
/retitle OCPBUGS-44960: (OSASINFRA-3643) bump k8s and dependencies |
@EmilienM: This pull request references Jira Issue OCPBUGS-44960, 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@EmilienM: This pull request references Jira Issue OCPBUGS-44960, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request. 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. |
/retest-required |
1 similar comment
/retest-required |
77450c0
to
0903b33
Compare
/test e2e-aws |
And again we have this error:
I thought we fixed that in |
* Ignition to 2.18.0 * openshift/api and client-go to the most recent commit on November 18th 2024. * k8s to v0.31.1 * CAPI to v1.8.4 * controller-runtime to v0.19.0 And then run `go mod tidy && go mod vendor`, `make update` and `UPDATE=true go test ./...`.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: EmilienM 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 |
@EmilienM: 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. |
Changes in
go.mod
:github.com/distribution/reference
github.com/openshift/api
andclient-go
to latestgithub.com/openshift/library-go
to latestgithub.com/prometheus/common
tov0.55.0
v0.31.1
v1.8.5
sigs.k8s.io/controller-runtime
tov0.19.0
Then code changes to adjust with the new versions.