Red Hat Bugzilla – Bug 1302831
Hooks can remain set after a stack operation is stopped
Last modified: 2016-04-26 16:23:06 EDT
+++ This bug was initially created as a clone of Bug #1302828 +++
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.
A simple workaround exists: just clear the hooks and everything will proceed. However, the problem is almost impossible to diagnose.
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.