Bug 1434639

Summary:	51-hosts fails to properly exit after executing
Product:	Red Hat OpenStack	Reporter:	Joe Talerico <jtaleric>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Joe Talerico <jtaleric>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	10.0 (Newton)	CC:	aschultz, jcoufal, jeder, mburns, ohochman, rhel-osp-director-maint, tvignaud
Target Milestone:	ga	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	All
OS:	Linux
Whiteboard:	aos-scalability-35
Fixed In Version:	openstack-tripleo-heat-templates-7.0.0-0.20170616123155.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 21:18:38 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 Joe Talerico 2017-03-22 00:41:22 UTC

Description of problem:
Once I hit 242 nodes in CNCF, 51-hosts became unreliable. 

Version-Release number of selected component (if applicable):
OSP10GA
os-collect-config-5.1.0-1.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Scale to a large number of overcloud nodes, (32-40 nodes at a time)

Actual results:
51-hosts never completes running

Expected results:
51-hosts populates /etc/hosts, and exits with the proper return code.

Additional info:
https://bugs.launchpad.net/tripleo/+bug/1674732

To get around this, I simply add a exit 0 at the top of 51-hosts on all my previously deployed nodes. Then manually add in the compute nodes to the cluster.

Comment 1 Alex Schultz 2017-06-20 14:47:19 UTC

This has already been addressed in 12 by the upstream bugs

Comment 7 errata-xmlrpc 2017-12-13 21:18:38 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:3462