Bug 1740946

Summary:	[RFE] TLS Everywhere cannot be deployed in a pre-deployed nodes because nova isn't configured on the undercloud
Product:	Red Hat OpenStack	Reporter:	Andrew Mercer <amercer>
Component:	openstack-tripleo-heat-templates	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Jeremy Agee <jagee>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	acanan, amcleod, asalvati, dcadzow, dmendiza, dvd, hjensas, jagee, mburns, nkinder, rcritten, rheslop, rmascena, sbaker, sputhenp
Target Milestone:	beta	Keywords:	FutureFeature, Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	docs-accepted
Fixed In Version:	openstack-tripleo-heat-templates-11.3.2-0.20200608073443.f604618.el8ost	Doc Type:	Enhancement
Doc Text:	With this update, you can deploy pre-provisioned nodes with TLSe by using the new 'tripleo-ipa' method.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-29 07:49:26 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:
Bug Blocks:	1838796

Description Andrew Mercer 2019-08-13 23:26:21 UTC

Description of problem:

When attempting to deploy the Overcloud for a Distributed Compute Node environment with TLS Everywhere the deploy fails due to an attempt to contact the Undercloud's Metadata service (169.254.169.254), but it is not reachable in a DCN configuration in a spine/leaf configuration.


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

OSP13z7


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:

Unable to retrieve metadata from config drive.


Expected results:


Additional info:

Comment 1 Andrew Mercer 2019-08-13 23:29:42 UTC

a couple of related bz's

(OSP15) https://bugzilla.redhat.com/show_bug.cgi?id=1633782
(OSP14) https://bugzilla.redhat.com/show_bug.cgi?id=1635370

Comment 15 errata-xmlrpc 2020-07-29 07:49:26 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-2020:3148