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
Failed ci: Pod can not be created: create pod test-pod ... in cluster default: Unauthorized #27919
Comments
/sig testing |
this is impacting multiple jobs, do we know what changed that caused this, and can that change be reverted? |
I believe this was not caused by any code change. The root cause is that Kubernetes external secret ran into a weird state and refused to sync the kubeconfig secret from GCP secret manager to the Prow service cluster. It's now mitigated by restarting the Kubernetes external secret deployment. Longer term fix is expected in #24869 More detailed are on Slack https://kubernetes.slack.com/archives/C7J9RP96G/p1667877096344719 |
/close |
@chaodaiG: 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/test-infra repository. |
Thank you very much!! |
What happened:
Pod can not be created: create pod test-pod ... in cluster default: Unauthorized
Yesterday the CI was fine and today it reports this error.
I see that the ci image was updated yesterday by #27913, may be is this the reason?
What you expected to happen:
CI works normally
How to reproduce it (as minimally and precisely as possible):
Please provide links to example occurrences, if any:
https://prow.k8s.io/pr?query=is%3Apr+repo%3Akubernetes-sigs%2Fkwok+author%3Awzshiming+head%3Afeat%2Fcni
Anything else we need to know?:
#27913
The text was updated successfully, but these errors were encountered: