Mistral's retries ignore join logical state
Bug #1819418 reported by
Oleg Ovcharuk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
There is a strange behavior with mistral's retries: if join task fails because of it's child tasks, retries reexecute this join task and ignore it's logical state.
Example:
wf1:
task-defaults:
retry:
count: 1
delay: 0
tasks:
task1:
action: std.noop
on-success: join_task
task2:
action: std.fail
on-success: join_task
join_task:
action: std.noop
join: all
Expected result: join_task has ERROR state after retries; wf1 has state info "failed because of task2, join_task"
Actual result: join_task has SUCCESS state; wf1 has state info "failed because of task2"
Changed in mistral: | |
status: | New → Confirmed |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/642431 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=99ebc1b5f73 f2a3ffc3a44e2eb e1119cfb033719
Committed: https:/
Submitter: Zuul
Branch: master
commit 99ebc1b5f73f2a3 ffc3a44e2ebe111 9cfb033719
Author: Oleg Ovcharuk <email address hidden>
Date: Mon Mar 11 15:07:57 2019 +0300
Retries shouldn't execute if join task failed because of child task
Change-Id: Ideaa9938497f74 335af633044cb6e 98fbb1522d8
Closes-Bug: #1819418
Signed-off-by: Oleg Ovcharuk <email address hidden>