Comment 12 for bug 1959203

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/xena)

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)