Description of problem: Provisioning using a build interface is difficult today, as the primary interface registered for a host is the only one that is configured for PXE boot. If the build interface is registered on the new host as the primary, then the IP and MAC addresses get out of date if/when the build interface is removed. It also means the hostname and IP address are incorrect, as the host would need to be registered with the build hostname, which may cause further identity issues (e.g. with Puppet). Version-Release number of selected component (if applicable): 6.0.3 How reproducible: Always Steps to Reproduce: 1. Create a new dual-homed host with its usual primary hostname 2. Add an additional network build interface 3. PXE boot from the additional interface Actual results: No PXE boot menu available (will default to local boot). Expected results: PXE boots and identifies as the primary hostname consistently.
Is this not delivered in 6.1.0 with the provisioning NIC?
Upstream was not able to recreate this after 1.8. We therefore believe this bug is included in Satellite 6.2. I am closing this as NEXTRELEASE. Please verify this in 6.2, and re-open this if this release does not meet the needs.