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
Workflow was running but all of sudden unable to proceed,
looking through controller log we found
"Jan 20, 2025 @ 14:17:31.998","time=""2025-01-20T08:47:31.998Z"" level=info msg=""Processing workflow"" namespace=default workflow=hive-1698426951-cron-1737275400","6aa8356f-0e1f-4842-b7f1-8035a97e8c95"
"Jan 20, 2025 @ 14:17:52.598","time=""2025-01-20T08:47:52.598Z"" level=info msg=""Workflow processing has been postponed due to max parallelism limit"" key=default/hive-1698426951-cron-1737275400","6aa8356f-0e1f-4842-b7f1-8035a97e8c95"
We have configured parallelism limit to 10, but only reach max 8 in the past 24hrs before the issue happen
no controller restart in the past 24hr.
We are not sure what is the root cause, and this has happened only once so far.
We can mitigate this issue by allowing workflow to progress if its in parallelism mutex or having running state.
Since workflows that are running should already be in parallelism mutex and it should keep running
line
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?
Workflow was running but all of sudden unable to proceed,
looking through controller log we found
We have configured parallelism limit to 10, but only reach max 8 in the past 24hrs before the issue happen
no controller restart in the past 24hr.
We are not sure what is the root cause, and this has happened only once so far.
We can mitigate this issue by allowing workflow to progress if its in parallelism mutex or having running state.
Since workflows that are running should already be in parallelism mutex and it should keep running
line
argo-workflows/workflow/controller/controller.go
Line 869 in 7305c18
Version(s)
v3.5.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: