-
Notifications
You must be signed in to change notification settings - Fork 39k
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
[k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite} #35600
Comments
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-slow/1073/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10668/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-slow/1074/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10669/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-slow/1075/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10670/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-slow/1076/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10671/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-slow/1077/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10672/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-slow/1078/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10673/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10792/ Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
|
[FLAKE-PING] @eparis This flaky-test issue would love to have more attention. |
any updates on this flake @eparis? |
[FLAKE-PING] @eparis This flaky-test issue would love to have more attention. |
Cool. @MrHohn let's close this down and let the bot file one again if it happens. |
This test always failed in 1.5 upgrade builds. An example as this :https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-1.4-1.5-upgrade-cluster/12/. Checked logs and found we were actually running the old version Addon update e2e test(probably depends on the original version?) after upgrade. But because Addon Manager is upgraded to a newer version in 1.5 and does not take care of resources in non @saad-ali @krousey May triage it as a non blocker in the upgrade spreadsheet? |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-slow/10667/
Failed: [k8s.io] Addon update should propagate add-on file changes [Slow] {Kubernetes e2e suite}
The text was updated successfully, but these errors were encountered: