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

Bug 1572706

Summary:	os-collect-config should retry signaling success of a resource if it receives a 500 error message from heat
Product:	Red Hat OpenStack	Reporter:	Andreas Karis <akaris>
Component:	openstack-heat-templates	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	apevec, aschultz, emacchi, igallagh, lhh, mburns, slinaber, srevivo, tvignaud
Target Milestone:	async	Keywords:	Tracking, Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-heat-templates-0-0.16.1e6015dgit.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the heat configuration notification process would not retry if heat was temporarily unavailable during a stack action. The heat task would hang indefinitely waiting for a response and the action would timeout. This issue has been resolved by adding a notification process retry when the Heat API endpoint returns a 503 or 504.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 09:40:17 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:

Description Andreas Karis 2018-04-27 16:06:08 UTC

Description of problem:
os-collect-config should retry signaling success of a resource if it receives a 500 error message from heat

In a customer environment, we can observe the following behavior:

* Director services are making the undercloud churn a lot
* communication between heat and keystone breaks temporarily due to load on undercloud
* heat returns 500 code to the compute's os-collect-config when the latter signals the success of resource ComputeSshKnownHostsDeployment
* os-collect-config never tries to signal the success of that resource again

Expected results:
os-collect-config should retry

Comment 5 Alex Schultz 2019-06-21 21:06:56 UTC

Turns out I fixed this back in 2017.  https://review.opendev.org/#/c/519417/ So it's in openstack-heat-agents >= 1.5.1 which shipped with OSP13. I'll see about backporting this to OSP10.

Comment 8 errata-xmlrpc 2019-10-16 09:40:17 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-2019:3119