Bug 1372777

Summary: Consistent network device naming not working
Product: Red Hat Quickstart Cloud Installer Reporter: Antonin Pagac <apagac>
Component: fusor-installerAssignee: John Matthews <jmatthew>
Status: CLOSED ERRATA QA Contact: Antonin Pagac <apagac>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0CC: jmontleo, tsanders
Target Milestone: gaKeywords: Triaged
Target Release: 1.0   
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: 2016-09-13 16:38:05 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:
Attachments:
Description Flags
screenshot of fusor network devices none

Description Antonin Pagac 2016-09-02 15:46:55 UTC
Created attachment 1197242 [details]
screenshot of fusor network devices

Description of problem:
I'm seeing eth* instead of consistent naming. In previous composes on this bare metal machine the consistent device network naming was working,

Version-Release number of selected component (if applicable):
QCI-1.0-RHEL-7-20160901.5

How reproducible:
Reproduced twice on the same HW.

Steps to Reproduce:
1. Run fusor-installer
2.
3.

Actual results:
Network devices are shown as eth*

Expected results:
Consistent network device naming

Additional info:

Comment 1 Jason Montleon 2016-09-02 19:20:24 UTC
The RC compose was done with an outdated version of lorax. RCM has tagged the newer version into the compose tag and are creating a new RC compose.

Comment 3 Antonin Pagac 2016-09-06 14:12:01 UTC
Verified in:
QCI-1.0-RHEL-7-20160902.5
QCIOOO-8.0-RHEL-7-20160902.1

Comment 5 errata-xmlrpc 2016-09-13 16:38:05 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-2016:1862