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

Bug 1309817

Summary: Hooks can remain set after a stack operation is stopped
Product: Red Hat OpenStack Reporter: Scott Lewis <sclewis>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED CURRENTRELEASE QA Contact: Amit Ugol <augol>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: augol, mburns, rhel-osp-director-maint, sbaker, shardy, srevivo, ssainkar, zbitter
Target Milestone: asyncKeywords: TestOnly, ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1302828 Environment:
Last Closed: 2016-09-28 19:27:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1302828    
Bug Blocks: 1302831    

Comment 3 Zane Bitter 2016-03-10 14:28:39 UTC 
This should be fairly easy to reproduce with a simple stack (only one resource required).

- set a pre-update hook on a resource
- start a stack update
- wait for the workflow to reach the hook and pause
- restart heat-engine while heat is still waiting for the hook
- do another stack update, removing the pre-update hook from the environment (so that this update should not stop for the hook)
- ensure that the update completes

Previously, the last update would stop at the hook (even though it wasn't requested in the environment), although you couldn't tell that because nothing appeared in the events or 'heat hook-poll'.