ipxe.efi not in centos stream containers

[Will Szumski]

Release: Wallaby
Host OS: CentOS 8 stream

I've enabled Ironic with iPXE support. When PXE booting a baremetal node, it will attempt to chainload ipxe using the NBP: ipxe.efi. This however is not present in /tftpboot in the centos 8 stream ironic_pxe container. This is what I have:

```
$ cd /tftpboot
$ ls ipxe-*
ipxe-i386.efi ipxe-snponly-x86_64.efi ipxe-x86_64.efi
```

It seems like it would be good to at least make this configurable. I'm unsure if the default of ipxe.efi works for other operating systems. Should we copy ipxe-x86_64.efi to ipxe.efi on stream for compatibility? Or the other option is to make the default change depending on OS.

[Radosław Piliszek (yoctozepto)]

Could you check other distros as well?

[Mark Goddard (mgoddard)]

Complication: In Xena, Ironic changed the default UEFI NBP file to snponly.efi: https://docs.openstack.org/releasenotes/ironic/xena.html#relnotes-18-1-0-stable-xena-upgrade-notes

[Mark Goddard (mgoddard)]

UEFI & iPXE fails from Xena on Ubuntu (& presumably Debian), due to missing snponly.efi.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/kolla/+/828694

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/828700

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/kolla/+/828694
Committed: https://opendev.org/openstack/kolla/commit/909710d739f1d7d4c2ef0865ebc9338f260aaa5b
Submitter: "Zuul (22348)"
Branch: master

commit 909710d739f1d7d4c2ef0865ebc9338f260aaa5b
Author: Mark Goddard <email address hidden>
Date: Thu Feb 10 10:58:55 2022 +0000

    ironic: Fix UEFI & iPXE bootloader filenames

    When using Ironic with UEFI boot mode and iPXE booting, nodes will
    attempt to chainload iPXE using a Network Boot Program (NBP). This is
    configured in Ironic via [pxe] uefi_ipxe_bootfile_name, and the default
    since Xena is snponly.efi. In Wallaby and earlier releases, the default
    was ipxe.efi. These files need to be available in the /tftpboot
    directory of the ironic-pxe image.

    The current default of snponly.efi was not present for any supported
    distros. ipxe.efi was present for Debian/Ubuntu but not CentOS, which
    appends the architecture to the filename (e.g. ipxe-x86_64.efi).

    This change ensures that both ipxe.efi and snponly.efi exist in
    /tftpboot for all supported distributions, ensuring that both the
    current and previous Ironic defaults should work. Where these files have
    different names, we use symlinks to allow for any deployers overriding
    the filenames in configuration.

    Closes-Bug: #1959203

    Change-Id: I79e78dca550262fc86b092a036f9ea96b214ab48

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/kolla/+/828845

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/kolla/+/828846

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/kolla/+/828847

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/kolla/+/828847
Committed: https://opendev.org/openstack/kolla/commit/77d683caaaed46149d2323b5a94c0e73bef3241c
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit 77d683caaaed46149d2323b5a94c0e73bef3241c
Author: Mark Goddard <email address hidden>
Date: Thu Feb 10 10:58:55 2022 +0000

    ironic: Fix UEFI & iPXE bootloader filenames

    When using Ironic with UEFI boot mode and iPXE booting, nodes will
    attempt to chainload iPXE using a Network Boot Program (NBP). This is
    configured in Ironic via [pxe] uefi_ipxe_bootfile_name, and the default
    since Xena is snponly.efi. In Wallaby and earlier releases, the default
    was ipxe.efi. These files need to be available in the /tftpboot
    directory of the ironic-pxe image.

    The current default of snponly.efi was not present for any supported
    distros. ipxe.efi was present for Debian/Ubuntu but not CentOS, which
    appends the architecture to the filename (e.g. ipxe-x86_64.efi).

    This change ensures that both ipxe.efi and snponly.efi exist in
    /tftpboot for all supported distributions, ensuring that both the
    current and previous Ironic defaults should work. Where these files have
    different names, we use symlinks to allow for any deployers overriding
    the filenames in configuration.

    Closes-Bug: #1959203

    Change-Id: I79e78dca550262fc86b092a036f9ea96b214ab48
    (cherry picked from commit 909710d739f1d7d4c2ef0865ebc9338f260aaa5b)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/kolla/+/828846
Committed: https://opendev.org/openstack/kolla/commit/1ac4662c11b7baade1a1d689f5a8b40d481aa3ab
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 1ac4662c11b7baade1a1d689f5a8b40d481aa3ab
Author: Mark Goddard <email address hidden>
Date: Thu Feb 10 10:58:55 2022 +0000

    ironic: Fix UEFI & iPXE bootloader filenames

    When using Ironic with UEFI boot mode and iPXE booting, nodes will
    attempt to chainload iPXE using a Network Boot Program (NBP). This is
    configured in Ironic via [pxe] uefi_ipxe_bootfile_name, and the default
    since Xena is snponly.efi. In Wallaby and earlier releases, the default
    was ipxe.efi. These files need to be available in the /tftpboot
    directory of the ironic-pxe image.

    The current default of snponly.efi was not present for any supported
    distros. ipxe.efi was present for Debian/Ubuntu but not CentOS, which
    appends the architecture to the filename (e.g. ipxe-x86_64.efi).

    This change ensures that both ipxe.efi and snponly.efi exist in
    /tftpboot for all supported distributions, ensuring that both the
    current and previous Ironic defaults should work. Where these files have
    different names, we use symlinks to allow for any deployers overriding
    the filenames in configuration.

    Closes-Bug: #1959203

    Change-Id: I79e78dca550262fc86b092a036f9ea96b214ab48
    (cherry picked from commit 909710d739f1d7d4c2ef0865ebc9338f260aaa5b)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/kolla/+/828845
Committed: https://opendev.org/openstack/kolla/commit/af092df6aa66f58a8d3ad3b363db0d81f54c0944
Submitter: "Zuul (22348)"
Branch: stable/xena

commit af092df6aa66f58a8d3ad3b363db0d81f54c0944
Author: Mark Goddard <email address hidden>
Date: Thu Feb 10 10:58:55 2022 +0000

    ironic: Fix UEFI & iPXE bootloader filenames

    When using Ironic with UEFI boot mode and iPXE booting, nodes will
    attempt to chainload iPXE using a Network Boot Program (NBP). This is
    configured in Ironic via [pxe] uefi_ipxe_bootfile_name, and the default
    since Xena is snponly.efi. In Wallaby and earlier releases, the default
    was ipxe.efi. These files need to be available in the /tftpboot
    directory of the ironic-pxe image.

    The current default of snponly.efi was not present for any supported
    distros. ipxe.efi was present for Debian/Ubuntu but not CentOS, which
    appends the architecture to the filename (e.g. ipxe-x86_64.efi).

    This change ensures that both ipxe.efi and snponly.efi exist in
    /tftpboot for all supported distributions, ensuring that both the
    current and previous Ironic defaults should work. Where these files have
    different names, we use symlinks to allow for any deployers overriding
    the filenames in configuration.

    Closes-Bug: #1959203

    Change-Id: I79e78dca550262fc86b092a036f9ea96b214ab48
    (cherry picked from commit 909710d739f1d7d4c2ef0865ebc9338f260aaa5b)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 14.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 11.3.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 12.2.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 13.1.0 release.