Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1108981

Summary: [RFE][heat]: Stack Breakpoint
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED ERRATA QA Contact: Amit Ugol <augol>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: ddomingo, markmc, nbarcet, sbaker, shardy, yeylon
Target Milestone: gaKeywords: FutureFeature
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/stack-breakpoint
Whiteboard: upstream_milestone_kilo-rc1 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-heat-2015.1.0-3.el7ost Doc Type: Enhancement
Doc Text:
Heat now supports user hooks, which pause execution of stack operations at specified points to allow the user to insert their own actions into Heat's workflow. Hooks are attached to resources in the stack's environment file. Currently supported hook types are 'pre-create' and 'pre-update'.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:12:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-06-13 04:04:30 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/stack-breakpoint.

Description:

Troubleshooting a failed stack can be quite difficult. During development, debugging failed template is simply part of the process, but in production, a previously working template can also fail for many reasons. Providing support for troubleshooting template will not only increase productivity but will also help the adoption of Heat template.  Currently a stack is stopped after a resource fails in the create step, but this may be too late or too hard to debug because the original cause of the failure may not be obvious or the environment may have been changed.  If we can pause the stack at a point before the failure, then we are in a better position to troubleshoot.  For instance, we can check whether the state of the environment and the stack is what we expect, we can manually run the next step to see how it fails, etc. 
While developing new template or resource type, it is also useful to bring up a stack to a point before the new code is to be executed.  Then the developer can manually execute and debug the new code. 

Specification URL (additional information):

None
Comment 5 errata-xmlrpc 2015-08-05 13:12:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548