You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
I have searched existing issues and could not find a match for this bug
When I use the HTTP template, I find it pending all the time.
Then I saw that the workflow status was error, and encountered a transient error.
error is : failed to create Agent pod. Reason: Operation cannot be fulfilled on resourcequotas "xxxx": the object has been modified; please apply your changes to the latest version and try again
What did you expect to happen?
I hope to encounter transient errors that can be retried.
Version(s)
v3.4.17
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
None
Logs from the workflow controller
None
Logs from in your workflow's wait container
None
The text was updated successfully, but these errors were encountered:
agilgur5
changed the title
When creating an agent pod, if it is a transient error, it should be retried.
When creating an agent pod, transient error is not retried
Sep 24, 2024
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
What happened ?
When I use the HTTP template, I find it pending all the time.
Then I saw that the workflow status was error, and encountered a transient error.
error is :
failed to create Agent pod. Reason: Operation cannot be fulfilled on resourcequotas "xxxx": the object has been modified; please apply your changes to the latest version and try again
What did you expect to happen?
I hope to encounter transient errors that can be retried.
Version(s)
v3.4.17
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
None
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: