Bug 1298745

Summary:	Public interface for RHCI's and RHCS-I OOO ISO's default to eth0
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Thom Carlin <tcarlin>
Component:	ISO Installer	Assignee:	John Matthews <jmatthew>
Status:	CLOSED ERRATA	QA Contact:	Thom Carlin <tcarlin>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	jmontleo
Target Milestone:	ga	Keywords:	Triaged
Target Release:	1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-13 16:24:09 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 2016-01-14 22:14:44 UTC

Description of problem:

Installing ISOs on systems with public (external) interface that are not eth0 require boot menu changes

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

TP2

How reproducible:

100%

Steps to Reproduce:
1. Install ISO on system with public interface on eth2
2. When fusor*-installer comes up, examine fields

Actual results:

fields are blank and hostname = localhost.localdomain

Expected results:

Populated fields (including hostname)

Additional info:

External bz (1298268) is workaround.

Poor UX

Comment 1 Jason Montleon 2016-06-21 19:35:23 UTC

We no longer start any interfaces since enabling consistent network names. Further our design diagrams suggesting having the OOO and QCI hosts attached to a single routed network. In a case where that suggestion isn't followed the user may have some additional setup to do, but essentially no interface is different from another now.

Comment 2 Thom Carlin 2016-06-28 17:58:23 UTC

In QCI 1.2:
Verified no interfaces are started after either ISO
Verified consistent network names are now being used (no ethx)

Moving to VERIFIED

Comment 8 errata-xmlrpc 2016-09-13 16:24:09 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