-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Node should fail when there is ErrImagePull
#4229
Labels
Comments
ErrImagePull
ErrImagePull
ErrImagePull
I'm not 100% sure this is a bug. The node should say in pending if the pod is pending. Can you please attach the pod status? |
Pod status is pending. Container status is Waiting. It seems you are correct and it is not a bug as Kubernetes is trying (and retrying) to pull the image.
|
I am facing similar issue when our pods stay pending. Is there a way to config it to exit on ErrImagePull? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Prepared a workflow with a loop. Container being run in the loop can not be pulled as it does not exist. Kubernetes returns ErrImagePull.
What happened
Step is stuck in Pending status. Workflow is stuck in Running status.
Expected to happen
Step is failed, workflow is failed.
Diagnostics
What Kubernetes provider are you using?
With docker desktop for Mac
What version of Argo Workflows are you running?
Workflow to reproduce
kubectl get wf -o yaml loops-maps-8n25j
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: