Bug 1269995

Summary:	Nodes reconnection to the broker not working properly. Compute nodes are not registered again
Product:	Red Hat OpenStack	Reporter:	Giulio Fidente <gfidente>
Component:	openstack-puppet-modules	Assignee:	Ivan Chavero <ichavero>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	apevec, dnavale, emacchi, fdinitto, fpercoco, gfidente, ichavero, jeckersb, jguiditt, jschluet, lbezdick, lhh, lnatapov, mabaakou, majopela, markmc, mburns, mmagr, rhel-osp-director-maint, sclewis, sgordon, srevivo, ushkalim, yeylon, zhenqin
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-puppet-modules-2015.1.8-25.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1231885	Environment:
Last Closed:	2015-12-21 17:10:49 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:	1231885
Bug Blocks:	1185030, 1191185, 1251948, 1261487, 1271347

Comment 2 Giulio Fidente 2015-10-08 17:55:55 UTC

We need to backport into OPM the changes which permit usage of the "rabbit_heartbeat_timeout_threshold" param.

For nova, that is the commit at:
https://github.com/openstack/puppet-nova/commit/58e831ef093422ea0510e0198dd8f75d33523f26

We need the backport for:
nova
neutron
cinder
ceilometer
heat
keystone

Comment 4 Ivan Chavero 2015-10-14 06:50:44 UTC

All of this components are now in master OPM, backporting to Kilo.

Can i have qe ack please?

Comment 8 Lukas Bezdicka 2015-10-20 14:23:06 UTC

*** Bug 1273464 has been marked as a duplicate of this bug. ***

Comment 11 Leonid Natapov 2015-12-15 12:15:38 UTC

openstack-puppet-modules-2015.1.8-31.el7ost.noarch
unable to reproduce.

Comment 13 errata-xmlrpc 2015-12-21 17:10:49 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-2015:2677