Reviewed: https://review.openstack.org/418961 Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=12f734562c5925c9260a3f038d570a7910c51cfb Submitter: Jenkins Branch: master
commit 12f734562c5925c9260a3f038d570a7910c51cfb Author: Dougal Matthews <[email protected]> Date: Wed Jan 11 14:12:44 2017 +0000 Fail the deployment workflows when sending a "FAILED" message When Mistral workflows execute a second workflow (a sub-workflow execution), the parent workflow can't easily determine if sub-workflow failed. This is because the failure is communicated via a Zaqar message only and when a workflow ends with a successful Zaqar message it appears have been successful. This problem surfaces because parent workflows should have an "on-error" attribute but it is never called, as the workflow doesn't error. This change marks the workflow as failed if the message has the status "FAILED". Now when a sub-workflow fails, the task that called it should have the on-error triggered. Previously it would always go to on-success. Change-Id: Ic1781bcf3922da61d42970cf2b42c951f83f7a74 Related-Bug: #1651704 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651704 Title: Errors when starting introspection are silently ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ironic-inspector/+bug/1651704/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
