-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Bug 2033751: Rebase 1.23.0 #26711
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
Bug 2033751: Rebase 1.23.0 #26711
Conversation
d8dd022 to
caa97ba
Compare
|
@damemi: An error was encountered querying GitHub for users with public email (kewang@redhat.com) for bug 2033751 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: i/o timeout
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damemi, deads2k 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 |
|
/test e2e-gcp-csi Trying with new CI images. |
|
Rebase has landed, lets see if this brings new kapi/kubelet |
|
kube-apiserver is now 1.23 (kubelet is still 1.22.1 from 6859754). All test failures in e2e-gcp are timeouts /hold cancel |
|
Lot of the timeouts of storage tests are caused by an Ephemeral container not getting started. Do we have Ephemeral containers enabled? |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
I can see that EphemeralContainers were enabled as beta in 1.23, so we may have API server + KCM that has the feature enabled and kubelet that has it disabled -> test failure. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/hold let it pick up a new nightly for kubelet update |
|
force accepted a payload /test all |
|
New changes are detected. LGTM label has been removed. |
|
/hold cancel kubelet 1.23 was picked up |
|
CSI tests fail due to missing busybox image We only list |
mirrored /test e2e-gcp |
| "k8s.gcr.io/sig-storage/snapshot-controller:v3.0.2": -1, | ||
| "k8s.gcr.io/sig-storage/snapshot-controller:v4.0.0": -1, | ||
|
|
||
| "k8s.gcr.io/e2e-test-images/busybox:1.29-1": -1, |
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.
I think this would be easier to maintain if it were a few lines down with busybox:1.29-2
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.
nah, I prefer to have it next to sig-storage elements, b/c they are handled differently than that other busybox image, it's complicated 😓
|
Retesting to include #26745 for better error message |
|
/retest |
1 similar comment
|
/retest |
|
@damemi: 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/test-infra repository. I understand the commands that are listed here. |
|
Replaced with #26753 |
|
@soltysh: Closed this PR. 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. |
|
@damemi: This pull request references Bugzilla bug 2033751. 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. |
Depends on openshift/kubernetes#1087