Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1437334

Summary:	hooks aren't retrieved properly
Product:	Red Hat OpenStack	Reporter:	Thomas Hervé <therve>
Component:	python-heatclient	Assignee:	Thomas Hervé <therve>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	apevec, augol, brad, hjensas, jcoufal, jruzicka, jschluet, lbezdick, lruzicka, mburns, mschuppe, rhel-osp-director-maint, sathlang, shardy, slinaber, srevivo, therve, yprokule, zbitter
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-heatclient-1.8.0-2.el7ost	Doc Type:	Bug Fix
Doc Text:	After the optimization of event retrieval process, the 'openstack stack hook poll' command stopped returning pending hooks, even if they existed and should be returned. The problem was fixed. Now pending hooks are returned correctly.	Story Points:	---
Clone Of:	1436712	Environment:
Last Closed:	2017-05-17 20:16:10 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:	1436712
Bug Blocks:	1394025

Comment 5 Alan Pevec 2017-04-10 14:45:07 UTC

> RDO Ocata has this pinned to 1.8.0

That's coming from upstream upper-constraints.txt
so upstream CI is not running with that fix, even master is 1.8.0:
https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L495
So you need new heatclient release upstream.

> (either need to unpin in rdoinfo, backport for OSP 11, and/or tag in upstream)

Release upstream should be easy enough, just send request to openstack/releases for 1.8.1

Comment 10 errata-xmlrpc 2017-05-17 20:16:10 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/RHEA-2017:1245