Timeout policy doesn't work with retry policy properly

Bug #1764441 reported by Vitalii Solodilov on 2018-04-16
This bug report is a duplicate of:  Bug #1767352: Timeout must fail task without retry. Edit Remove
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Vitalii Solodilov

Bug Description

I think that all before the task policies must be executed when task was rerun.
For example, the following workflow will be stuck in RUNNING state:

version: '2.0'
name: wb
    type: direct

        action: std.async_noop
        timeout: 2
          delay: 0
          count: 2
          - task2
        action: std.echo output="Hi!"
        timeout: 3

Dougal Matthews (d0ugal) on 2018-04-16
Changed in mistral:
status: New → Confirmed
importance: Undecided → High
milestone: none → rocky-2
Changed in mistral:
assignee: nobody → Vitalii Solodilov (mcdoker18)

Fix proposed to branch: master
Review: https://review.openstack.org/561795

Changed in mistral:
status: Confirmed → In Progress

Change abandoned by Vitalii Solodilov (<email address hidden>) on branch: master
Review: https://review.openstack.org/561795

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

Other bug subscribers