Bug 1279576

Summary: [RFE] Display MAC address in fusor-installer
Product: Red Hat Quickstart Cloud Installer Reporter: Thom Carlin <tcarlin>
Component: fusor-installerAssignee: Jason Montleon <jmontleo>
Status: CLOSED ERRATA QA Contact: Antonin Pagac <apagac>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0CC: apagac, tsanders
Target Milestone: gaKeywords: FutureFeature, Triaged
Target Release: 1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-13 16:22:30 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: 1342594    

Description Thom Carlin 2015-11-09 19:16:06 UTC 
Description of enhancement:

For systems with multiple NICs, it is not always clear which NIC corresponds with a given MAC address.  Enhancement request is to display MAC address during launch-fusor-installer

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

TP1

Additional info:

Current:
----------------------------------------------------------------------

Please select NIC on which you want provisioning enabled:
1. eth0
2. eth1
3. eth2
4. eth3
[...]
2. Change network interface | eth1

Proposed:
----------------------------------------------------------------------

Please select NIC on which you want provisioning enabled:
1. eth0 (00:00:00:00:00:00)
2. eth1 (00:00:00:00:00:01)
3. eth2 (00:00:00:00:00:02)
4. eth3 (00:00:00:00:00:03)
[...]
2. Change network interface | eth1 (00:00:00:00:00:01)
Comment 1 John Matthews 2016-06-16 14:54:04 UTC 
Included in refactoring work jmontleo completed with fusor-installer.
Comment 2 Antonin Pagac 2016-06-27 10:13:29 UTC 
Verified, compose 20160624.t.0
Comment 8 errata-xmlrpc 2016-09-13 16:22:30 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