Closed skarna987 closed 6 days ago
I could reproduce it I can have a look.
Screenshot for original issue
Verify in the example logs
"test-workflow-kqxvv-113404891": {
"boundaryID": "test-workflow-kqxvv-3314254127",
"children": [
"test-workflow-kqxvv-1105926477"
],
"displayName": "[0]",
"finishedAt": null,
"id": "test-workflow-kqxvv-113404891",
"name": "test-workflow-kqxvv.onExit[0]",
"nodeFlag": {},
"phase": "Running",
"progress": "0/1",
"startedAt": "2024-05-14T13:04:43Z",
"templateScope": "local/test-workflow-kqxvv",
"type": "StepGroup"
},
StepGroup test-workflow-kqxvv-113404891
stuck at running phase (incorrect behaviour)
StepGroup's child node test-workflow-kqxvv-113404891
marked failed (correct behaviour)
workflow marked complete (correct behaviour)
@tczhao I was able to reproduce it and opened an MR with a possible solution
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?
Created a workflow with exit-handler. When exit-handler was running I terminated the workflow with
argo terminate -n <namespace> <workflow>
command. My expectation was that after termination all exit handler nodes would be in "Failed" phase. However the "StepGroup" and "Steps" type nodes were still in "Running" phase.Version
v3.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