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
A CronWorkflow running every 10 minutes occasionally gave the error `Stopped with strategy 'Terminate'' and detected cronworkflows_concurrencypolicy_triggered. We checked the workflow executed immediately afterwards and found no elements triggering concurrencyPolicy.
Looking at the failed workflow, it is interrupted 10 seconds after start (2024-12-18T05:00:10Z), but has not met the next schedule (2024-12-18T05:10:00Z) of CronWorkflow.
| 2024-12-18 05:00:00.436 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.436Z" level=warning msg="Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"monitor-argo-workflows-1734498000\": the object has been modified; please apply your changes to the latest version and try again Conflict" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.436 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.436Z" level=info msg="Re-applying updates on latest version and retrying update" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
The logs indicate that a conflict occurred while updating the workflow. Is it possible that the current workflow was terminated somewhere else?
Thanks for confirming.
No elements were found to interrupt this Workflow.
The Workflow manifest attached to the body of the Issue is for this and the immediate runtime, but it did not take long enough for the ConcurrencyPolicy to have any impact.
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?
A CronWorkflow running every 10 minutes occasionally gave the error `Stopped with strategy 'Terminate'' and detected cronworkflows_concurrencypolicy_triggered. We checked the workflow executed immediately afterwards and found no elements triggering concurrencyPolicy.
Failed Workflow
monitor-argo-workflows-1734498600.txt
Workflow immediately after
monitor-argo-workflows-1734498000.txt
Looking at the failed workflow, it is interrupted 10 seconds after start (2024-12-18T05:00:10Z), but has not met the next schedule (2024-12-18T05:10:00Z) of CronWorkflow.
Version(s)
v3.6.2
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: