Mistral loses context of some tasks in error cases

Bug #2020370 reported by Oleg Ovcharuk
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress

Bug Description

Mistral loses context of some tasks in case there are errors in workflow execution.
Let me show 2 examples:

      action: std.noop
          b1: 1
      on-success: join_task
      action: std.noop
      join: all
          join_task: 2
          join_task: 1
      action: std.noop
          bs: 1
        - b2
        - b3
      action: std.noop
          b2: 1
      on-success: join_task
      action: std.fail
          b3: 1
      on-success: join_task

Expected context:
{\"bs\": 1, \"b2\": 1, \"b1\": 1, \"join_task\": 1, \"b3\": 1}
Actual context:
{\"b1\": 1, \"join_task\": 1, \"bs\": 1, \"b3\": 1}

Changed in mistral:
status: New → In Progress
Oleg Ovcharuk (vgvoleg)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/mistral

This issue was fixed in the openstack/mistral release candidate.

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.