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
My guess is that one of your workflows has non-ascii characters in it that are upsetting sqllite. It's unclear if they're actually an invalid unicode escape sequence.
Possibly in something like the description of the workflow.
Can you look at the workflows in the cluster and work out which one(s) it might be and attach (a redacted version) of them. Ideally in a zip or tar file so as not to lose any bad escape characters via copy and pasting into github.
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 upgrading from v3.5.6 to v3.5.11, we see the following error in the Argo UI whenever trying to list
Succeeded
orFailed
workflows:argo-server logs show the following:
Note also the following:
Our DB for archived workflows is Postgres 9.6.
We have the following defined in
workflow-controller-configmap
Version(s)
v3.5.11
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.
This is in our production environment immediately after updating to 3.5.11
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: