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
After updating to the latest version of Argo Workflows (3.6.2), I am encountering a fatal error related to concurrent map access when using custom gauges and histograms. The issue appears to stem from the gauge metrics, leading to a panic and crashing the workflow-controller.
Upgraded 5 days ago to 3.6
4 panics observed since the update
Over a thousand workflows have ran since the upgrade
The issue appears to be a rare occurrence which indicates it would be only be reproducible in certain conditions where there are a lot of workflows running
Version(s)
v3.6.x
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.
Here is an example of custom metrics we are using.
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?
After updating to the latest version of Argo Workflows (3.6.2), I am encountering a fatal error related to concurrent map access when using custom gauges and histograms. The issue appears to stem from the gauge metrics, leading to a panic and crashing the workflow-controller.
Version(s)
v3.6.x
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.
Here is an example of custom metrics we are using.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: