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
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.
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
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