<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Nikolay, thanks for sharing this…<div class=""><br class=""></div><div class="">I think that we really have a semantical ambiguity here. If we leave just “break-on” that both types of behavior have a right to exist.</div><div class=""><br class=""></div><div class="">I’m personally for defining that more explicitly with two separate instructions “success-on” and “error-on”. A use case for “success-on” may be, for example, checking a completion of another parallel task and if it’s completed then we can treat our task successful meaning that we already got what’s required. I know it sounds a little bit generic but still pointful for me.</div><div class=""><br class=""><div class="">
<div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 03 Mar 2015, at 19:47, Nikolay Makhotkin <<a href="mailto:nmakhotkin@mirantis.com" class="">nmakhotkin@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello,<div class=""><br class=""></div><div class="">Recently we've found that break_on property of RetryPolicy is not working now.</div><div class=""><br class=""></div><div class="">I tried to solve this problem but faced the another problem: How does 'break_on' supposed to work?</div><div class=""><br class=""></div><div class="">Will 'break_on' change the task state to ERROR or SUCCESS?<br class="">if ERROR, it means 'we interrupt all retry iterations and keep the state which was before'. </div><div class="">But if SUCCESS, it means 'we interrupt all retry iterations and assume SUCCESS state from task because we cought this condition'.</div><div class=""><br class=""></div><div class="">This is ambiguous.</div><div class=""><br class=""></div><div class="">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'.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><div class=""><div class=""><br class=""></div>-----<br class=""><div class=""><div dir="ltr" class=""><div class=""><font class="">Best Regards,</font></div><div class=""><font class="">Nikolay</font></div><div class=""><font class="">@Mirantis Inc.</font></div></div></div>
</div></div></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>