Bug 1434639 - 51-hosts fails to properly exit after executing
Summary: 51-hosts fails to properly exit after executing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 10.0 (Newton)
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ga
: 12.0 (Pike)
Assignee: Emilien Macchi
QA Contact: Joe Talerico
URL:
Whiteboard: aos-scalability-35
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-22 00:41 UTC by Joe Talerico
Modified: 2018-02-05 19:04 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170616123155.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 21:18:38 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1674450 0 None None None 2017-03-24 19:24:04 UTC
Launchpad 1674732 0 None None None 2017-03-22 00:41:22 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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
Note You need to log in before you can comment on or make changes to this bug.