Description of problem: When there are multiple NICs with multiple DHCP env, the target host will attempt to PXE boot to the DHCP env belonging to the first NIC. Version-Release number of selected component (if applicable): How reproducible: Easy to reproduce by creating a new VM and manually editing the /etc/libvirt/qemu/VMx.xml file. Steps to Reproduce: 1.When creating VMs (target host) assign two+ NICs to the VM. Assign lower slot number to the first NIC belonging to non provisioning DHCP and assign higher slot number to the provisioning NIC. For example - assign slot 3 for a public network NIC (which has a DHCP PXE env) and assign slot 7 to the NIC that is being planned for provisioning using staypuft. 2.When booted up in PXE boot mode, both the NICs will PXE boot in order, but will try to PXE boot to the DHCP env belonging to public domain and eventually fail. 3.When you reverse the slot number (set provisioning NIC to slot 3) the provisioning NIC will start to PXE boot and go into foreman discovery mode. Actual results: With multiple NICs, PXE boot is attempted to the DHCP env of the first NIC Expected results: Should ignore other NICs and only PXE boot of the provisioning NIC Additional info:
This is notabug, it's environmental. There is nothing we can do to change this, it's all in the configuration of vms/hardware. There isn't even a discovery image to do anything with at this point.