Retry policy break-on property does not work
Bug #1428576 reported by
Nikolay Makhotkin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Nikolay Makhotkin | ||
Kilo |
Fix Released
|
Medium
|
Nikolay Makhotkin | ||
Liberty |
Fix Released
|
Medium
|
Nikolay Makhotkin |
Bug Description
if we define something like
...
task1:
policies:
count: 5
delay: 4
break-on: <% true %>
it won't break the iteration of retries.
Moreover, there is ambiguity in 'break-on': we don't exactly know what task state will be - SUCCESS or ERROR.
Decided to use 'error-on' and 'success-on' for explicitly changing state.
Changed in mistral: | |
milestone: | 1.0.0 → none |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/161658
Review: https:/