[Flaking Test] ci-kubernetes-e2e-capz-master-windows.Overall

[AdminTurnedDevOps]

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

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[wendy-ha18]

/sig windows

[jsturtevant]

this error Error: "capz-conf-etj4t6-kubeconfig" not found in namespace "default": secrets "capz-conf-etj4t6-kubeconfig" not found is printed out while the cluster is starting up and is not an error in the test.

we are tracking the other flakes in #125187

/close

[k8s-ci-robot]

@jsturtevant: Closing this issue.

In response to this:

this error Error: "capz-conf-etj4t6-kubeconfig" not found in namespace "default": secrets "capz-conf-etj4t6-kubeconfig" not found is printed out why the cluster is starting up and is not an error in the test.

we are tracking the other flakes in #125187

/close

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.