Open Stack

Hello,

Recently we've found that break_on property of RetryPolicy is not working
now.

I tried to solve this problem but faced the another problem: How does
'break_on' supposed to work?

Will 'break_on' change the task state to ERROR or SUCCESS?
if ERROR, it means 'we interrupt all retry iterations and keep the state
which was before'.
But if SUCCESS, it means 'we interrupt all retry iterations and assume
SUCCESS state from task because we cought this condition'.

This is ambiguous.

There is a suggestion to use not just 'break_on' but, say, another, more
explicit properties which will delete this ambiguity. For example,
'success_on' and 'error_on'.

Thoughts?

-----
Best Regards,
Nikolay
@Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150303/4edbcf71/attachment.html>