This bug has been found while investigating https://bugzilla.redhat.com/show_bug.cgi?id=1434509 We used hooks on the UpdateDeployment resources while making a minor update. The first and/or second hooks generally worked fine, but we were waiting forever on the last 2. The heat hook-poll -n5 overcloud command didn't return anything. It turns out the client detection of hooks is broken. We don't set the stack_name of the event correctly, and as we use the stack_name to identify the event, we can't detect the hooks correctly. This affects the heat command line client (openstack stack hook poll / heat hook-poll).
This might be related: https://bugs.launchpad.net/python-heatclient/+bug/1675035
Patch merged in upstream stable/newton.
Verified with python-heatclient-1.5.0-3.el7ost.noarch
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/RHBA-2017:1589