Skip to content
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

Closed
wzshiming opened this issue Nov 8, 2022 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@wzshiming
Copy link
Member

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

@wzshiming wzshiming added the kind/bug Categorizes issue or PR as related to a bug. label Nov 8, 2022
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Nov 8, 2022
@MadhavJivrajani
Copy link
Contributor

/sig testing

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Nov 8, 2022
@liggitt
Copy link
Member

liggitt commented Nov 8, 2022

this is impacting multiple jobs, do we know what changed that caused this, and can that change be reverted?

@chaodaiG
Copy link
Contributor

chaodaiG commented Nov 8, 2022

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

@chaodaiG
Copy link
Contributor

chaodaiG commented Nov 8, 2022

/close

@k8s-ci-robot
Copy link
Contributor

@chaodaiG: Closing this issue.

In response to this:

/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/test-infra repository.

@sbueringer
Copy link
Member

Thank you very much!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Development

No branches or pull requests

6 participants