Join tasks work incorrect after rerun

Bug #1833262 reported by Oleg Ovcharuk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Fix Released
High
Oleg Ovcharuk

Bug Description

Let's consider this example:

wf1:
type: direct
tasks:
  t0:
    action: std.noop
    on-success:
      - t3
  t1:
    action: std.http url=some_unstable_url
    on-success:
      - t3
  t2:
    action: std.http url=some_unstable_url
    on-success:
      - t3
  t3:
    action: std.noop
    join: all

HTTP actions failed for the first execution, we fixed this url and decided to rerun t1 and t2.

Rerun of t1:
Expected result: t2 and t3 are still in ERROR state
Actual result: t3 is in SUCCESS state, ignoring it's logical state

Rerun of t2 after previous rerun:
Expected result: all tasks are in SUCCESS state, t3 has 1 action execution
Actual result: t3 has 2 action executions

Oleg Ovcharuk (vgvoleg)
summary: - Join tasks works incorrect after rerun
+ Join tasks work incorrect after rerun
Changed in mistral:
assignee: nobody → Oleg Ovcharuk (vgvoleg)
importance: Undecided → High
milestone: none → ussuri-1
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to mistral (master)

Reviewed: https://review.opendev.org/666016
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=bdbfb823010cefe94945ba118199d9ecccdbcab7
Submitter: Zuul
Branch: master

commit bdbfb823010cefe94945ba118199d9ecccdbcab7
Author: Oleg Ovcharuk <email address hidden>
Date: Tue Jun 18 20:00:05 2019 +0300

    Reformat rerun logic for tasks with join

    Change-Id: I055bc2d5a4bdf839f1e262e49563616d8deff92f
    Closes-Bug: #1833262
    Signed-off-by: Oleg Ovcharuk <email address hidden>

Changed in mistral:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/mistral 10.0.0.0b1

This issue was fixed in the openstack/mistral 10.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.