Mistral

The task execution "has_next_tasks" field is not calculated properly

Bug #1829841 reported by Renat Akhmerov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Fix Released
Critical
Renat Akhmerov
Mistral train-1 "train-1"

Bug Description

The following test will lead to hanging:

wf:
  tasks:
    task1:
      action: std.fail
      on-error:
        - noop

It happens because "has_next_tasks" field is not calculated properly in mistral/engine/tasks.py module because of the typo (misplaced "]" char).

Renat Akhmerov (rakhmerov)
Changed in mistral:
assignee: nobody → Renat Akhmerov (rakhmerov)
milestone: none → train-1
importance: Undecided → Critical
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to mistral (master)

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

commit a477fe49cdccb4ce34f665b26127e96565da285f
Author: Renat Akhmerov <email address hidden>
Date: Tue May 21 17:18:25 2019 +0700

    Fix how "has_next_tasks" is calculated for task executions

    * There was a weird typo in the list generator expression made in
      https://review.opendev.org/#/c/652575 that led to calculating
      a field value in the wrong way. Fixed. The added test was
      previously failing.

    Closes-Bug: #1829841

    Change-Id: I6b8ea8dfa623acbb56f649630ddee62e43d484eb

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

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

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

Other bug subscribers

Remote bug watches

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