Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1769103

Summary:	Overcloud deployed nodes are coming up with relative NIC names instead of the actual names
Product:	Red Hat OpenStack	Reporter:	Darin Sorrentino <dsorrent>
Component:	openstack-tripleo	Assignee:	James Slagle <jslagle>
Status:	CLOSED DUPLICATE	QA Contact:	Arik Chernetsky <achernet>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15.0 (Stein)	CC:	aschultz, bfournie, mburns
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-07 20:59:38 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 Darin Sorrentino 2019-11-05 22:31:07 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Darin Sorrentino 2019-11-05 22:36:53 UTC

Sorry, I am not sure what happened, BZ posted the bug before I was able to actually add any details.  WHen I introspect the nodes, I can see the interface names:

(undercloud) [stack@director15 introspection_data]$ cat server20.introspection | jq .inventory.interfaces[].name
"enp7s0"
"enp6s0"
(undercloud) [stack@director15 introspection_data]$ 

However when I deploy the overcloud-full.qcow2 image, the interfaces are showing up as "eth0" and "eth1".  So when I configure my templates to use the device names "enp6s0" and "enp7s0", the deployment fails because it does not find those interfaces.

Comment 2 Bob Fournier 2019-11-07 20:59:38 UTC

I believe you are hitting https://bugzilla.redhat.com/show_bug.cgi?id=1759430, which is a problem in OSP-15 GA, it will be fixed in the z2 release.

*** This bug has been marked as a duplicate of bug 1759430 ***