Bug 1643386

Summary:	[OSP14] Vendordata plugins are not fully functional for tls-everywhere scenario
Product:	Red Hat OpenStack	Reporter:	Martin Schuppert <mschuppe>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Schuppert <mschuppe>
Status:	CLOSED ERRATA	QA Contact:	Archit Modi <amodi>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	14.0 (Rocky)	CC:	jslagle, mbooth, mburns, mschuppe
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-nova-13.3.1-0.20181013120142.8ab435c.el7ost openstack-tripleo-heat-templates-9.0.1-0.20181013060873.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:54: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:

Description Martin Schuppert 2018-10-26 07:14:31 UTC

Description of problem:

A recent change making nova-metadata-api work with wsgi [1][2] moved the vendordata plugin parameters to the nova::metadata manifest. While this is conceptually correct as nova-metadata is the one that should be using this parameters. In practice, this doesn't work once you deploy the nova-metadata-api separate from nova-compute. This is because this parameters are used in the compute drivers (in the ironic driver, for instance).

[1] https://review.openstack.org/#/c/582621/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1579866

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

How reproducible:
always

Steps to Reproduce:
1. master/rocky deploy of a tls-everywhere env
2. overcloud nodes fail to get metadata vendordata information from novajoin

Actual results:
overcloud nodes fail to get metadata vendordata information from novajoin

Expected results:
overcloud nodes get metadata vendordata information from novajoin and overcloud installation is successful

Additional info:

Comment 9 errata-xmlrpc 2019-01-11 11:54: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/RHEA-2019:0045