Bug 1372777 - Consistent network device naming not working
Summary: Consistent network device naming not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-installer
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 1.0
Assignee: John Matthews
QA Contact: Antonin Pagac
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 15:46 UTC by Antonin Pagac
Modified: 2016-09-13 16:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 16:38:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
screenshot of fusor network devices (275.57 KB, image/png)
2016-09-02 15:46 UTC, Antonin Pagac 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1862 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.0 2016-09-13 20:18:48 UTC

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
Note You need to log in before you can comment on or make changes to this bug.