Bug 1436712

Summary: hooks aren't retrieved properly
Product: Red Hat OpenStack Reporter: Thomas Hervé <therve>
Component: python-heatclientAssignee: Thomas Hervé <therve>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: high Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: augol, brad, hjensas, jjoyce, jruzicka, lbezdick, mburns, mschuppe, rhel-osp-director-maint, sathlang, shardy, srevivo, therve, yprokule, zbitter
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-heatclient-1.5.0-3.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1437334 (view as bug list) Environment:
Last Closed: 2017-06-28 15:25:46 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:    
Bug Blocks: 1434509, 1437334    

Description Thomas Hervé 2017-03-28 13:36:34 UTC
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).

Comment 2 Brad P. Crochet 2017-03-29 12:10:11 UTC
This might be related: https://bugs.launchpad.net/python-heatclient/+bug/1675035

Comment 3 Zane Bitter 2017-04-06 22:50:27 UTC
Patch merged in upstream stable/newton.

Comment 8 Yurii Prokulevych 2017-06-26 14:56:42 UTC
Verified with python-heatclient-1.5.0-3.el7ost.noarch

Comment 10 errata-xmlrpc 2017-06-28 15:25:46 UTC
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