Description of problem: Ironic introspection loops over ipxe.efi for UEFI boot_mode Version-Release number of selected component (if applicable): RH OSP 10 How reproducible: Always Steps to Reproduce: 1. Start the ironic node introspection 2. Node loops at PXE booting after downloading ipxe.efi 3. Actual results: Node loops at PXE booting by downloading ipxe.efi Expected results: Node should continue with introspection process. Additional info: To reproduce the issue in lab, I added dhcp-match=set:efi,option:client-arch,9 as well.
The fix is changing dhcp-boot=tag:efi,ipxe.efi to dhcp-boot=tag:efi,tag:!ipxe,ipxe.efi
upstream patch proposed - https://review.openstack.org/#/c/499750/
Newton upstream patch - https://review.openstack.org/#/c/502365/
*** Bug 1464523 has been marked as a duplicate of this bug. ***
I have another customer that seems to be hitting this issue attaching screenshot of where their remote console is looping on introspection with UEFI.
Created attachment 1337961 [details] screenshot of loop
stphilli - its likely, would have to see a tcpdump of the dhcp transactions to know for sure. We recommend making the change to /etc/ironic-inspector/dnsmasq.conf as shown above. The fix has merged upstream and should be in next 10.z release.
stphilli it looks like a networking issue to me. PXE boot itself didn't start in the first place and this bug resolves PXE boot loop.
installed latest osp10 with puddle 2017-10-30.3 on 11/1/2017 This bug has been verified environment: [stack@undercloud ~]$ rpm -qa | grep puppet-ironic- puppet-ironic-9.5.0-2.el7ost.noarch dnsmasq.conf file appears updated [stack@undercloud ~]$ sudo cat /etc/ironic-inspector/dnsmasq.conf port=0 interface=br-ctlplane bind-interfaces dhcp-range=192.168.0.100,192.168.0.120,29 dhcp-sequential-ip dhcp-match=ipxe,175 dhcp-match=set:efi,option:client-arch,7 dhcp-match=set:efi,option:client-arch,9 # Client is already running iPXE; move to next stage of chainloading dhcp-boot=tag:ipxe,http://192.168.0.1:8088/inspector.ipxe # Client is PXE booting over EFI without iPXE ROM; send EFI version of iPXE chainloader dhcp-boot=tag:efi,tag:!ipxe,ipxe.efi # Client is running PXE over BIOS; send BIOS version of iPXE chainloader dhcp-boot=undionly.kpxe,localhost.localdomain,192.168.0.1 [stack@undercloud ~]$ openstack baremetal introspection bulk start Setting nodes for introspection to manageable... Starting introspection of manageable nodes Started Mistral Workflow. Execution ID: a97a2b8f-be30-43c6-9b43-1e5776be905d Waiting for introspection to finish... Introspection for UUID a3002942-c5c7-4d23-aba8-aa4cee4adf17 finished successfully. Introspection for UUID 34ac3467-6ce6-4191-bfdc-13a2163e4b39 finished successfully. Introspection completed. Setting manageable nodes to available... Started Mistral Workflow. Execution ID: bcdbcbb2-99a7-4dea-b7fc-5499b31514c0 [stack@undercloud ~]$ openstack baremetal introspection bulk status +--------------------------------------+----------+-------+ | Node UUID | Finished | Error | +--------------------------------------+----------+-------+ | 34ac3467-6ce6-4191-bfdc-13a2163e4b39 | True | None | | a3002942-c5c7-4d23-aba8-aa4cee4adf17 | True | None | +--------------------------------------+----------+-------+ [stack@undercloud ~]$ ironic node-list +--------------------------------------+------+---------------+-------------+--------------------+-------------+ | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | +--------------------------------------+------+---------------+-------------+--------------------+-------------+ | 34ac3467-6ce6-4191-bfdc-13a2163e4b39 | None | None | power off | available | False | | a3002942-c5c7-4d23-aba8-aa4cee4adf17 | None | None | power off | available | False | +--------------------------------------+------+---------------+-------------+--------------------+-------------+
I made 2 minor edits to doc text, otherwise it looks fine. - changed iPxE to iPXE - removed "over PXE"
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/RHBA-2017:3231