-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.5.6 Logs flooded with Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io
#13149
Comments
Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io
@vermaxik have u tried on v3.5.8? |
unfortunately, the issue is still persist in 3.5.8. |
@vermaxik can you change the workflow controller command line to have --loglevel debug and share logs? |
Seeing as no-one else is seeing this issue so far I suspect you have some local configuration causing a problem. Your cluster appears quite busy, does this also happen when you're running fewer workflows? #12574 seems the most likely candidate for causing this, but I don't know why you're affected and others aren't, and I'm not sure it's the problem. |
Hello! This is logs of the one workflow from ~100 with debug enabled.
|
@vermaxik do u have INFORMER_WRITE_BACK set to false by any chance? |
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 you expected to happen?
After upgrading to 3.5.6 we can see in logs a lot of warning of
The issue was separated from #13140
Version
3.5.6
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows 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: