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
Wait and main (server) containers terminate when the parent Workflow's client container has completed pinging the main (server) container.
The non-working sequence with Windows daemons:
Init container completes.
Wait and main (server) containers start.
Wait and main (server) containers remain stuck in Running:
Also in some cases, deleting the workflow from Argo fails to remove the daemon's pod. The pod can only be removed by kubectl -n argo delete pod <pod-name> --grace-period=0 --force
Version
3.5.7
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.
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?
Continuing from the discussion #13146.
The working sequence with Linux daemons:
The non-working sequence with Windows daemons:
Also in some cases, deleting the workflow from Argo fails to remove the daemon's pod. The pod can only be removed by
kubectl -n argo delete pod <pod-name> --grace-period=0 --force
Version
3.5.7
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
#13146 (reply in thread)
Logs from in your workflow's wait container
#13146 (reply in thread)
The text was updated successfully, but these errors were encountered: