Bug 1389972

Summary:	Traceback in error log during heat-engine service shutdown
Product:	Red Hat OpenStack	Reporter:	VIKRANT <vaggarwa>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0 (Liberty)	CC:	lruzicka, mburns, nshetty, rhel-osp-director-maint, sbaker, shardy, srevivo
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	8.0 (Liberty)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-heat-5.0.3-1.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, when heat-engine was terminated during startup, it tried to clean up processes that had not been started. Consequently, heat-engine reported and logged the "NoneType" attribute error. This behaviour has been corrected, and heat-engine now shuts down gracefully.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-14 15:25:48 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:	1409638
Bug Blocks:

Description VIKRANT 2016-10-30 05:53:24 UTC

Description of problem:

Traceback in error log during heat-engine service shutdown.

Cu is hitting the same issue during the overcloud deployment and they are suspecting that deployment is getting failed due to this issue. 

Upstream Bug 

https://bugs.launchpad.net/heat/+bug/1562042

Version-Release number of selected component (if applicable):
RHEL OSP 8

How reproducible:
Most of the time for Cu. 

Steps to Reproduce:
1.
2.
3.

Actual results:
Deployment getting failed. 

Expected results:
Deployment should get completed without any issue.

Additional info:

Upstream Bug fix is already present in OSP 9 version [1]
Request to backport this fix in OSP 8.

[1] https://access.redhat.com/downloads/content/rhel---7/x86_64/5036/openstack-heat-engine/6.0.0-11.el7ost/noarch/fd431d51/package-changelog

Comment 1 Zane Bitter 2016-10-31 14:09:02 UTC

The fix is present in the upstream 5.0.2 release, so we have the option of picking it up in a rebase.

Comment 4 Amit Ugol 2017-03-28 10:10:52 UTC

Latest is already in 5.0.3, fix is in it.

Comment 8 errata-xmlrpc 2017-06-14 15:25:48 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/RHSA-2017:1456