-
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
Daemon containers not getting destroyed when enabling POD_NAMES as v2 #8692
Labels
Comments
@JPZ13 could you take a look please? |
The bug is in this line of code:
Should be something like this: podName := util.PodName(woc.wf.Name, childNode.Name, childNode.TemplateName, childNode.ID, util.GetWorkflowPodNameVersion(woc.wf))
woc.controller.queuePodForCleanup(woc.wf.Namespace, podName, terminateContainers) @KesavanKing would you like to submit a PR to fix? |
Sure |
Sorry I didn't see this earlier. Happy to review your PR @KesavanKing |
terrytangyuan
pushed a commit
that referenced
this issue
May 11, 2022
Signed-off-by: i342464 <[email protected]>
sarabala1979
pushed a commit
that referenced
this issue
Aug 8, 2022
Signed-off-by: i342464 <[email protected]> Signed-off-by: Saravanan Balasubramanian <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Summary
What happened/what you expected to happen?
With POD_NAMES v2
Started workflow controller with env POD_NAMES v2
Created a simple daemon container. Workflow succeeded but the daemon container was still running.
When I check the logs no kill signal is sent to the daemon pod.
Without POD_NAMES v2
When i remove the env , the kill signal is properly sent to the daemon pod. Daemon pod name might not constructed properly
What version are you running? : 3.3.5
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Logs with POD_NAME v2
Logs without POD_NAME v2
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: