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

Fix already existing random job name. #20

Closed
Carreau opened this issue May 15, 2017 · 1 comment
Closed

Fix already existing random job name. #20

Carreau opened this issue May 15, 2017 · 1 comment

Comments

@Carreau
Copy link
Member

Carreau commented May 15, 2017

Matthias Bussonnier @Carreau 09:52
Morning/Evening all, when running helm upgrade ... I get a
 Error: jobs.batch "pull-all-nodes-<mynamespace>-1" already exists
Any clue why, and what I can do ?

Matthias Bussonnier @Carreau 09:58
Response : kubectl delete jobs pull-all-nodes-<mynamespace>-1 --namespace=<mynamespace>
and job were list-able with kubectl get jobs --namespace=<mynamespace>

Yuvi Panda @yuvipanda 10:00
thanks @Carreau
that seems to happen when a helm install or upgrade is interrupted, or when you re-install into same namespace. should fix them both
can you open an issue in the helm-chart repo?

Matthias Bussonnier @Carreau 10:01
Yep. Seem to be the case when the docker image is huge. I got a timeout but the kubectl --namespace=<YOUR_NAMESPACE> get pod listed them as successful after a few minutes.
@yuvipanda
Copy link
Collaborator

This has been fixed, we now put the timestamp in there too.

consideRatio pushed a commit that referenced this issue Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants