Skip to content
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

Controller pods must be deleted and restarted to pick up new retention policy #11194

Open
2 of 3 tasks
bwmetcalf opened this issue Jun 9, 2023 · 9 comments
Open
2 of 3 tasks
Labels
area/controller Controller issues, panics P3 Low priority type/bug

Comments

@bwmetcalf
Copy link

bwmetcalf commented Jun 9, 2023

Pre-requisites

  • I have double-checked my configuration
  • I can confirm the issues exists when I tested with :latest
  • I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

Using

% helm list -n argo
NAME          	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART                	APP VERSION
argo-workflows	argo     	14      	2023-06-09 15:48:03.550419949 +0000 UTC	deployed	argo-workflows-0.28.2	v3.4.8

After making a change to the helm values and redeploying, the new retention policy settings do not take effect until the controller pods are deleted. It seems the controller code should pick up the new configmap configuration automatically. Perhaps it does but not in a timely manner?

Version

3.4.8

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.

We can see this from the output of `argo list`.  After updating the retention policy, the behavior remains the same until the controller pods are cycled.

Logs from the workflow controller

n/a

Logs from in your workflow's wait container

n/a
@bwmetcalf
Copy link
Author

I can confirm that the controller does not pick up new settings after at least 2 hours.

@sarabala1979
Copy link
Member

fixed in #10218

@sarabala1979
Copy link
Member

can you try with latest

@sarabala1979 sarabala1979 added the P3 Low priority label Jun 15, 2023
@bwmetcalf
Copy link
Author

Thanks @sarabala1979! We'll update and report back. It looks like the code changes will indeed fix the issue.

@bwmetcalf
Copy link
Author

@sarabala1979 Is there a release planned soon so we can move this fix to our production environments. I haven't tried latest yet as we prefer to use tagged releases. Just getting back from vacation and following up. Thanks!

@terrytangyuan
Copy link
Member

It should be available in v3.4.8

@bwmetcalf
Copy link
Author

3.4.8 is the version we are using which exhibited the problem which led to me creating this issue. I see #10218 was merged a while back, but it seems to have not fixed our issue.

@bwmetcalf
Copy link
Author

It looks like some refactoring has taken place since the above MR as the code now lives here https://github.com/argoproj/argo-workflows/blob/dc56332e6a4de71dd0ec0af9bd8a2b9686e550b4/workflow/controller/controller.go#L406C4-L406C4 and is a bit different from the original MR.

@tooptoop4
Copy link
Contributor

i think this can be closed, stakater/reloader handles this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/controller Controller issues, panics P3 Low priority type/bug
Projects
None yet
Development

No branches or pull requests

5 participants