Open jakkubu opened 1 month ago
This is an edge case that isn't handled in the current code. the current workflow-controller will only validate the deadline for a suspended workflow if a running suspend node exists.
I believe we need to have a deadline checking logic here and mark workflow phase fail https://github.com/argoproj/argo-workflows/blob/e11e664d92677b8addffae90b3238f867b091024/workflow/controller/operator.go#L327-L330
What happened? What did you expect to happen?
Reproduce:
activedeadlineSeconds
passed (100s)running
stateExpectation 1: In step 4 workflow should fail after
activeDeadlineSeconds
pass.I can imagine that this may be expected behaviour. This is questionable, and in our use case doesn't make sense. However in such case the following steps should succeed:
Expectation 2: In step 6
activeDeadlineSeconds
should not fail and the deadline timer should be stopped for effective suspend time (workflow in suspend and running steps done).Again: Expectation 1 is what would be most logical for me. In such case Expectation 2 would make no sense.
Version(s)
v3.5.11, v3.6.0-rc1, c9b093cf1844fad034f6b5a6a73a353bcfed5c7fe53ca10b4bd7f11b6483cd25
Paste a minimal 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