Red Hat Bugzilla – Bug 1464523
Unable to introspect/provision UEFI enabled KVM machines with Ironic
Last modified: 2017-09-19 14:24:47 EDT
Description of problem:
When trying to introspect or provision KVM VMs with UEFI enabled, Ironic times out.
The VM console looks like it's looping over the NICs, trying to pxeboot each of them. I can see DHCP being picked up, then ipxe.efi, and then it just hops to the next NIC, until the introspection times out for the node.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. deploy undercloud
2. create some UEFI enabled VMs and register them
3. try to run introspection
as described above
please see https://bugzilla.redhat.com/show_bug.cgi?id=1462351 for the details about how KVM/libvirt were set up to ensure UEFI works and does PXEboot.
Could you please provide details on how exactly you've set your KVM VMs with UEFI?
Also please try tcpdump-ing br-ctlplane to catch the DHCP traffic.
The domxml for the VM in use is at https://bugzilla.redhat.com/show_bug.cgi?id=1462351#c4
You can simply generate a VM with proper configs by installing RHEL7.4, OVMF and running virt-install --boot uefi
I don't have a reproducer handy to get the dumps atm, but I'll have something set up when some more urgent stuff is finished
Dan - any luck in reproducing this?
(In reply to Bob Fournier from comment #4)
> Dan - any luck in reproducing this?
every single time I tried.
Dan - can you try the workaround here to dnsmasq.conf?https://bugzilla.redhat.com/show_bug.cgi?id=1479386
Dan - I'm marking this is as a dup of 1479386 which fixes an introspection UEFI issue. From the description this sounds very similar - DHCP works and the ipxe.efi is downloaded but it never proceeds past that as the dnsmasq.conf will keep providing ipxe.efi if EFI is set.
If the problem still occurs even with the fix for 1479386 or a workaround to change the settings in /etc/ironic/dnsmasq.conf. then please reopen this.
*** This bug has been marked as a duplicate of bug 1479386 ***
*** This bug has been marked as a duplicate of bug 1489192 ***