<div dir="ltr"><div>Hi Mark,</div><div><br></div><div>There was some issue with the cleaning image due to which the issue reported in previous conversation was observed.</div><div><br></div><div>This was successfully resolved.</div><div>By setting the parameter in ironic.conf file</div><div><div style="font-family:verdana,sans-serif">[pxe]</div><div style="font-family:verdana,sans-serif">uefi_ipxe_bootfile_name = ipxe-x86_64.efi</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">The "node provide" command successfully executed and the node came in "available" state.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><b>In Legacy:</b></div><div style="font-family:verdana,sans-serif">When I am trying to create the server using "server create " command and a userimage is passed in the command, the procedure is that the node will install userimage over the network and then will be rebooted</div><div style="font-family:verdana,sans-serif">After the reboot, it will boot up with the Hard disk and with the OS specified in userimage.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><b>In UEFI:</b></div><div style="font-family:verdana,sans-serif"><div>When I am trying to create the server using "server create " command and a userimage is passed in the command, the procedure of installing user image and rebooting remains the same.</div><div>But After the reboot, despite setting the hard disk as the first priority, it again starts booting over the network and eventually fails.</div><div><br></div><div>I have also tried passing the <b style="font-style:italic">capabilities='boot_option:local' </b>both in baremetal node and flavor, but the behaviour is the same.</div><div><br></div><div>Regards</div><div>Anirudh Gupta</div><div><br></div></div><div style="font-family:verdana,sans-serif"><br></div></div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 16, 2021 at 2:54 PM Anirudh Gupta <<a href="mailto:anyrude10@gmail.com" target="_blank">anyrude10@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Mark,</div><div><br></div><div>Thanks for your reply. Yes, I am using Centos 8 only.</div><div><br></div><div>I tried changing the settings and restarted the docker container.</div><div><br></div><div>The cleaning process moved a step further but it started showing the error <b>"Could not select: Exec format not supported"</b></div><div><b><br></b></div><div><img src="cid:ii_ksef67f12" alt="image.png" width="541" height="369"><br></div><div><br></div><div>Regards</div><div>Anirudh Gupta</div><div><br></div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 16, 2021 at 1:52 PM Mark Goddard <<a href="mailto:mark@stackhpc.com" target="_blank">mark@stackhpc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:verdana,sans-serif">Hi Anirudh,</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Are you using CentOS 8? The iPXE EFI bootloader file is named ipxe-x86_64.efi there, so a TFTP request for ipxe.efi will fail.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Could you try setting the following in ironic.conf:</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">[pxe]</div><div style="font-family:verdana,sans-serif">uefi_ipxe_bootfile_name = ipxe-x86_64.efi</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">If this works, we should change it in kolla-ansible. Would you be able to propose the change via Gerrit?</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Mark</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 13 Aug 2021 at 17:18, Anirudh Gupta <<a href="mailto:anyrude10@gmail.com" target="_blank">anyrude10@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Team,<div><br></div><div>I am trying to provision Baremetal node using IRONIC with KOLLA-ANSIBLE.</div><div>I have enabled the support of "IPXE" in kolla-ansible as well.</div><div><br></div><div>I am getting an issue that when my baremetal node is booted in UEFI Mode, it is not able to find file <b>"ipxe.efi"</b> as a result of which cleaning of the node fails</div><div><br></div><img src="cid:ii_ksa4lw2h0" alt="image.png" width="497" height="83"><br><div><br></div><div>But when I change the BIOS Mode of my Baremetal Node to Legacy.BIOS, it looks for the file "<b>undionly.kpxe"</b> for which the acknowledgment is received and Data Packets are transferred. Eventually the cleaning of node is also a success.</div><div><br></div><div><img src="cid:ii_ksa4povw1" alt="image.png" width="497" height="193"><br></div><div><br></div><div>Is there any limitation of IRONIC or KOLLA-ANSIBLE side that provisioning of Baremetal Node can only be done in Legacy Bios Mode?</div><div>For bare metal provisioning in UEFI mode, is there any other parameter that needs to be enabled.</div><div><br></div><div>Regards</div><div>Anirudh Gupta</div><div><br></div></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div></div>