Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1434639 - 51-hosts fails to properly exit after executing
51-hosts fails to properly exit after executing
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
10.0 (Newton)
All Linux
urgent Severity urgent
: ga
: 12.0 (Pike)
Assigned To: Emilien Macchi
Joe Talerico
aos-scalability-35
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-21 20:41 EDT by Joe Talerico
Modified: 2018-02-05 14:04 EST (History)
7 users (show)

See Also:
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 16:18:38 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1674450 None None None 2017-03-24 15:24 EDT
Launchpad 1674732 None None None 2017-03-21 20:41 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Joe Talerico 2017-03-21 20:41:22 EDT
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 10:47:19 EDT
This has already been addressed in 12 by the upstream bugs
Comment 7 errata-xmlrpc 2017-12-13 16:18:38 EST
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.