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

k8s-infra-prow: job fails to launch #2559

Closed
ameukam opened this issue Aug 16, 2021 · 4 comments
Closed

k8s-infra-prow: job fails to launch #2559

ameukam opened this issue Aug 16, 2021 · 4 comments
Labels
area/apps/prow k8s-infra-prow.k8s.io, code in apps/prow/ area/prow Setting up or working with prow in general, prow.k8s.io, prow build clusters kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@ameukam
Copy link
Member

ameukam commented Aug 16, 2021

Part of #1394

Periodic job k8s-infra-prow-heartbeat fails to launch and is stuck in Triggered.

/area prow
/area apps/prow
milestone v1.23

@k8s-ci-robot k8s-ci-robot added area/prow Setting up or working with prow in general, prow.k8s.io, prow build clusters area/apps/prow k8s-infra-prow.k8s.io, code in apps/prow/ labels Aug 16, 2021
@spiffxp
Copy link
Member

spiffxp commented Sep 2, 2021

/priority important-soon
/kind bug
/milestone v1.23

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/bug Categorizes issue or PR as related to a bug. labels Sep 2, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Sep 2, 2021
ameukam added a commit to ameukam/k8s.io that referenced this issue Sep 23, 2021
Ref: kubernetes#2559
Part of kubernetes#1475

It's possible the kubeconfig is incorrectly parsed. Testing this theory.

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
@ameukam
Copy link
Member Author

ameukam commented Sep 24, 2021

@eddiezane with some custom debugging(see #2788) identified the issue : The cluster name in the kubeconfig stored as secret was incorrect.

I updated the GCP secret with a new version of the kubeconfig:

gcloud secrets versions add k8s-infra-build-clusters-kubeconfig --data-file=./prow-build-clusters-kubeconfig.yaml --project kubernetes-public 

@ameukam
Copy link
Member Author

ameukam commented Sep 24, 2021

/close

@k8s-ci-robot
Copy link
Contributor

@ameukam: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/apps/prow k8s-infra-prow.k8s.io, code in apps/prow/ area/prow Setting up or working with prow in general, prow.k8s.io, prow build clusters kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants