[Kolla-Ansible][Ironic] Baremetal node Cleaning fails in UEFI mode, but succeeds in Legacy Bios Mode

Anirudh Gupta anyrude10 at gmail.com
Fri Aug 20 07:21:17 UTC 2021


Hi Mark,

There was some issue with the cleaning image due to which the issue
reported in previous conversation was observed.

This was successfully resolved.
By setting the parameter in ironic.conf file
[pxe]
uefi_ipxe_bootfile_name =  ipxe-x86_64.efi

The "node provide" command successfully executed and the node came in
"available" state.

*In Legacy:*
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
After the reboot, it will boot up with the Hard disk and with the OS
specified in userimage.

*In UEFI:*
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.
But After the reboot, despite setting the hard disk as the first priority,
it again starts booting over the network and eventually fails.

I have also tried passing the *capabilities='boot_option:local' *both in
baremetal node and flavor, but the behaviour is the same.

Regards
Anirudh Gupta




On Mon, Aug 16, 2021 at 2:54 PM Anirudh Gupta <anyrude10 at gmail.com> wrote:

> Hi Mark,
>
> Thanks for your reply.  Yes, I am using Centos 8 only.
>
> I tried changing the settings and restarted the docker container.
>
> The cleaning process moved a step further but it started showing the error *"Could
> not select: Exec format not supported"*
>
> [image: image.png]
>
> Regards
> Anirudh Gupta
>
>
>
> On Mon, Aug 16, 2021 at 1:52 PM Mark Goddard <mark at stackhpc.com> wrote:
>
>> Hi Anirudh,
>>
>> 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.
>>
>> Could you try setting the following in ironic.conf:
>>
>> [pxe]
>> uefi_ipxe_bootfile_name =  ipxe-x86_64.efi
>>
>> If this works, we should change it in kolla-ansible. Would you be able to
>> propose the change via Gerrit?
>>
>> Mark
>>
>> On Fri, 13 Aug 2021 at 17:18, Anirudh Gupta <anyrude10 at gmail.com> wrote:
>>
>>> Hi Team,
>>>
>>> I am trying to provision Baremetal node using IRONIC with KOLLA-ANSIBLE.
>>> I have enabled the support of "IPXE" in kolla-ansible as well.
>>>
>>> I am getting an issue that when my baremetal node is booted in UEFI
>>> Mode, it is not able to find file *"ipxe.efi"* as a result of which
>>> cleaning of the node fails
>>>
>>> [image: image.png]
>>>
>>> But when I change the BIOS Mode of my Baremetal Node to Legacy.BIOS, it
>>> looks for the file "*undionly.kpxe"* for which the acknowledgment is
>>> received and Data Packets are transferred. Eventually the cleaning of node
>>> is also a success.
>>>
>>> [image: image.png]
>>>
>>> Is there any limitation of IRONIC or KOLLA-ANSIBLE side that
>>> provisioning of Baremetal Node can only be done in Legacy Bios Mode?
>>> For bare metal provisioning in UEFI mode, is there any other parameter
>>> that needs to be enabled.
>>>
>>> Regards
>>> Anirudh Gupta
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210820/52eeaf8f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 200447 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210820/52eeaf8f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 91313 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210820/52eeaf8f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 126227 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210820/52eeaf8f/attachment-0005.png>


More information about the openstack-discuss mailing list