-
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
Pod argo-server still keeps restarting, even after #2249 #2355
Comments
@alexec Related to your previous PRs |
Additional info: I tried to replicate the exact same watch behaviour with kubectl, in verbose mode:
and then I will re-run now the command with Update: yep, I confirm, it's a server side timeout that breaks the Watch:
|
@simster7 there is a bug in the code, but I do not have bandwidth to fix. My suggestion - either (1) flag around the restart code so people can disable it if it is a problem or (2) find a proper fix. |
I think this is a duplicate of #2090 |
Closed as dup. |
I'll see if I can find a fix |
Can this be relevant? kubernetes/client-go#547 |
I think this should be the main issue, since it's relevant to the bug being described as opposed to the feature implementation in general. Reopening |
@simster7 thanks a lot for the quick fix! I can confirm that in the last ~12 hours there were no restarts since I deployed 2.6.1. |
Wooo! |
Checklist:
What happened:
#2249 still happens, it's not fixed.
After upgrading to Argo 2.6.0, the
argo-server
pod keeps restarting with exit code 0, with the following message:What you expected to happen:
The underlying ConfigMap was never modified, so argo-server should not restart to reload the config, as it did not even change.
I tried 2 scenarios:
How to reproduce it (as minimally and precisely as possible):
Install default manifest, wait up to 1 hour, see that the pod restarts.
Anything else we need to know?:
AWS EKS 1.14 platform
Environment:
Argo version: 2.6.0
Kubernetes version :
Other debugging information (if applicable):
Here's a screenshot about the restart frequency:
Logs
These are the latest logs, when the referenced ConfigMap is deleted (workflow-controller-configmap)
Previous logs when the empty, default ConfigMap existed:
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: