Reviewed: https://review.openstack.org/315476 Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=530544b3df7513a132c0b81e5c1b6a802959cb1f Submitter: Jenkins Branch: master
commit 530544b3df7513a132c0b81e5c1b6a802959cb1f Author: Steven Hardy <email address hidden> Date: Wed May 11 18:56:41 2016 +0100
Add deployment ID to deploy signal events
Curently you get events that look like this with the default event formatter:
2016-05-11 17:49:12 [0]: SIGNAL_IN_PROGRESS Signal: deployment succeeded
Including the ID in the reason string will help (particularly in the case of failure), as you can then easily show the deployment and thus the stderr associated with the failure.
Change-Id: I59a3e9bf527040c4d807adc4f822bfa2c1591585 Related-Bug: #1564627
Reviewed: https:/ /review. openstack. org/315476 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=530544b3df7 513a132c0b81e5c 1b6a802959cb1f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 530544b3df7513a 132c0b81e5c1b6a 802959cb1f
Author: Steven Hardy <email address hidden>
Date: Wed May 11 18:56:41 2016 +0100
Add deployment ID to deploy signal events
Curently you get events that look like this with the default
event formatter:
2016-05-11 17:49:12 [0]: SIGNAL_IN_PROGRESS Signal: deployment succeeded
Including the ID in the reason string will help (particularly in the
case of failure), as you can then easily show the deployment and
thus the stderr associated with the failure.
Change-Id: I59a3e9bf527040 c4d807adc4f822b fa2c1591585
Related-Bug: #1564627