<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Dear Anirudh,<div>I do remember I also had some odd behaviour with HPE ProLiant DL380 Gen10 server when using UEFI boot. I was using bifrost to deploy the server with Kayobe (before deploying the cloud services).</div><div>I could overcome the issue by adding capability "boot_mode:uefi" to the node. So my complete capability string was "cpu_vt:true,cpu_aes:true,cpu_hugepages:true,cpu_hugepages_1g:true,cpu_txt:true,boot_option:local,boot_mode:uefi"</div><div>Using guide Ironic Advanced Features Guide [1].</div><div><br></div><div>Hope this helps</div><div><br></div><div><br></div><div>[1] <a href="https://docs.openstack.org/ironic/wallaby/install/advanced.html">https://docs.openstack.org/ironic/wallaby/install/advanced.html</a></div><div><br></div><div><br></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 23 Aug 2021 at 20:24, Anirudh Gupta <<a href="mailto:anyrude10@gmail.com">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 Julia,</div><div><br></div><div>Thanks for your reply.</div><div><br></div><div>There is also an update that with Centos 8.4 Partition Disk Image, I am able to successfully provision the baremetal node. With Centos 8.4 ISO and Wholedisk Image the behaviour is the same that it doesn't boot from Hard disk.</div><div><br></div><div>Please find below my setup details:</div><div><br></div><div>I am using <span style="color:rgb(32,31,30);font-family:Calibri,sans-serif;font-size:14.6667px"><span style="margin:0px;padding:0px;border:0px;font-style:inherit;font-variant:inherit;font-stretch:inherit;font-size:9pt;line-height:inherit;font-family:Arial,sans-serif;vertical-align:baseline;color:black"><b>HP server DL380 Gen9</b></span><span style="font-weight:inherit;margin:0px;padding:0px;border:0px;font-style:inherit;font-variant:inherit;font-stretch:inherit;font-size:9pt;line-height:inherit;font-family:Arial,sans-serif;vertical-align:baseline;color:black"> with </span><span style="margin:0px;padding:0px;border:0px;font-style:inherit;font-variant:inherit;font-stretch:inherit;font-size:9pt;line-height:inherit;font-family:Arial,sans-serif;vertical-align:baseline;color:black"><b>BIOS P89 v2.76 (10/21/2019)</b></span><span style="font-weight:inherit;margin:0px;padding:0px;border:0px;font-style:inherit;font-variant:inherit;font-stretch:inherit;font-size:9pt;line-height:inherit;font-family:Arial,sans-serif;vertical-align:baseline;color:black"> </span><span style="margin:0px;padding:0px;border:0px;font-style:inherit;font-variant:inherit;font-stretch:inherit;font-size:9pt;line-height:inherit;font-family:Arial,sans-serif;vertical-align:baseline;color:black">with </span></span><b>IPMI</b> utility</div><div><br></div><div>Hard disk is the first priority followed by 1GB NIC which I have set to PXE</div><div><br></div><div>I don't find any logs in /var/log/ironic/deploy_logs. However there is a folder <i><b>/var/log/kolla/ironic/</b></i>, but there are no deploy_logs in that folder</div><div><br></div><div>I have downloaded the kolla source image from docker hub</div><div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div>docker pull kolla/centos-source-ironic-conductor:wallaby</div><div><br></div></blockquote>Similar images have been downloaded by kolla ansible for other ironic components<br><br>Regards<div>Anirudh Gupta<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 20, 2021 at 9:56 PM Julia Kreger <<a href="mailto:juliaashleykreger@gmail.com" target="_blank">juliaashleykreger@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 dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 20, 2021 at 7:07 AM 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>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></div></div></blockquote><div><div>This is very very likely an issue with the vendor's firmware. We've seen some instances where the bmc refuses to honor the request to change *or* where it is honored for a single boot operation only. In part some of this may be due to improved support in handling UEFI boot signaling where the wrong thing could occur, at least with IPMI. </div><div><br></div><div>In order to create a fix or workaround, we need the following information:</div><div><br></div><div>Are you using IPMI or Redfish? If your using IPMI, you should consider using Redfish.</div><div><br></div><div>What is the hardware vendor?</div><div><br></div><div>What is the BMC firmware version?</div><div><br></div><div>Is the BMC set to always network boot by default completely?</div><div><br></div><div>In UEFI, what does the machine report for the efibootmgr output. Your deployment agent logs actually have this output already in the journal. Typically /var/log/ironic/deploy_logs. We've seen some hardware act completely disjointed from the EFI NVRAM, or where it resets the EFI NVRAM when we request a one time override.</div><div><br></div><div>Most importantly, what is the version of ironic and ironic-python-agent?</div></div><div> </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><div style="font-family:verdana,sans-serif"><div></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 class="gmail_attr">[trim]</div></div></div>
</blockquote></div></div>
</blockquote></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br></div><div>බුද්ධික සංජීව ගොඩාකුරු </div><div>Buddhika Sanjeewa Godakuru </div><div><br></div><div>Systems Analyst/Programmer </div><div>Deputy Webmaster / University of Kelaniya</div><div><br></div><div>Information and Communication Technology Centre (ICTC) </div><div>University of Kelaniya, Sri Lanka, </div><div>Kelaniya, </div><div>Sri Lanka. </div><div><br></div><div>Mobile : (+94) 071 5696981 </div><div>Office : (+94) 011 2903420 / 2903424 </div></div></div></div></div>
<br>
<div><font size="2">++++++++++++++++++++++++++++++<wbr>++++++++++++++++++++++++++++++<wbr>++ </font></div><span style="font-size:1.3em">University of Kelaniya Sri Lanka, accepts no liability for the
content of this email, or for the consequences of any actions taken on
the basis of the information provided, unless that information is
subsequently confirmed in writing. If you are not the intended
recipient, this email and/or any information it contains should not be
copied, disclosed, retained or used by you or any other party and the
email and all its contents should be promptly deleted fully from our
system and the sender informed.
</span><br>
<br><span style="font-size:1.3em">E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete.
</span><br>
<br><span style="font-size:1.3em">++++++++++++++++++++++++++++++</span><span style="font-size:1.3em"><wbr>++++++++++++++++++++++++++++++</span><span style="font-size:1.3em"><wbr>+
</span><br>