Bug 1302827 - Hooks can remain set after a stack operation is stopped
Summary: Hooks can remain set after a stack operation is stopped
Keywords:
Status: CLOSED DUPLICATE of bug 1302828
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: z4
: 7.0 (Kilo)
Assignee: Zane Bitter
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 18:03 UTC by Zane Bitter
Modified: 2016-04-26 14:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-28 18:06:46 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-01-28 18:03:19 UTC

Description Zane Bitter 2016-01-28 18:03:19 UTC
If a thread is cancelled (including if heat-engine is restarted) while a user hook (aka breakpoint) is active, the hook is still marked as active in the database. If the user modifies the environment to disable the hook, then the next time Heat reaches the point in traversing the stack where the hook was invoked Heat will pause and wait for the hook to be cleared; however there will be no log message to indicate that the hook was invoked, nor a corresponding event in the event list, nor any indication from the "hook-poll" command that the hook is active.

Comment 1 Zane Bitter 2016-01-28 18:06:46 UTC

*** This bug has been marked as a duplicate of bug 1302828 ***


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