Bug 1309817 - Hooks can remain set after a stack operation is stopped
Summary: Hooks can remain set after a stack operation is stopped
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 7.0 (Kilo)
Assignee: Zane Bitter
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On: 1302828
Blocks: 1302831
TreeView+ depends on / blocked
 
Reported: 2016-02-18 18:46 UTC by Scott Lewis
Modified: 2016-09-28 19:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1302828
Environment:
Last Closed: 2016-09-28 19:27:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1538733 0 None None None 2016-02-18 18:46:18 UTC

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'.


Note You need to log in before you can comment on or make changes to this bug.