-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
[Flaking Test] ci-kubernetes-e2e-capz-master-windows.Overall #125240
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/sig windows |
this error we are tracking the other flakes in #125187 /close |
@jsturtevant: Closing this 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 kubernetes-sigs/prow repository. |
Which jobs are flaking?
master-informing
capz-windows-master
Which tests are flaking?
ci-kubernetes-e2e-capz-master-windows.Overall
Since when has it been flaking?
It's been failing consecutively since 5/29. Even when the test shows up green, if you click on it, it shows that it still couldn't find the secret.
Testgrid link
https://testgrid.k8s.io/sig-release-master-informing#capz-windows-master
Reason for failure (if possible)
Error: "capz-conf-etj4t6-kubeconfig" not found in namespace "default": secrets "capz-conf-etj4t6-kubeconfig" not found
Anything else we need to know?
It looks to me like Azure Identity isn't creating an appropriate secret that's needed.
Relevant SIG(s)
/sig-windows
@kubernetes/release-team-release-signal
The text was updated successfully, but these errors were encountered: