Bug 1571818

Summary: Cloud-init randomly fail to get nova metadata
Product: Red Hat OpenStack Reporter: Marian Krcmarik <mkrcmari>
Component: python-novajoinAssignee: Ade Lee <alee>
Status: CLOSED ERRATA QA Contact: Prasanth Anbalagan <panbalag>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: chjones, dciabrin, hrybacki, jschluet, michele, rcritten, rmascena
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-novajoin-1.0.18-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:53:37 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 Marian Krcmarik 2018-04-25 13:13:35 UTC
Description of problem:
From time to time it seems that we experience contention on novajoin, which makes cloud-init fail to retrieve metadata when doing:

curl -s http://169.254.169.254/openstack/2016-10-06/vendor_data2.json

To workaround the chances of contention we currently have a random sleep before that call so lower the odds that many nodes call novajoin at the same time.

This random sleep reduces the failure rate at deploy time but we can still experience it fairly often.

The end result often is that overcloud nodes end up without cert and overcloud deployment fails, the probability raises with number of nodes

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


How reproducible:
often

Steps to Reproduce:
1. Deploy overcloud of Openstack with TLS everywhere.

Actual results:
Overcloud deployment fails since some certs are missing on some overcloud nodes


Additional info:

Comment 1 Damien Ciabrini 2018-04-25 14:46:38 UTC
Proposed https://review.openstack.org/#/c/564137/3 to overcome the failures.

Comment 9 errata-xmlrpc 2018-06-27 13:53:37 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-2018:2086