Please backport https://review.opendev.org/c/openstack/puppet-ironic/+/797683 to OpenStack 16.2 We have a need to support UEFI/iPXE-only x86_64 compute nodes within the same overcloud as IBM Power compute nodes (which require legacy PXE support, and cannot use iPXE). Currently the deploy will only support either the IBM Power compute, or the UEFI x86_64 compute, but not both at the same time. This has to go into the OSP 16 series since OSP 16.2 will be the last version of RedHat OpenStack supported on IBM Power (due to chances in Power10 combined with changes in RHEL9), thus we would not be able to use this fix in an OSP 17 deploy.
It took a while until I fully understand the context of this RFE. So requrement here is to set both pxe/ipxe_bootfile_name + pxe/uefi_ipxe_config_template and pxe/pxe_bootfile_name + pxe/uefi_pxe_config_template so that ironic can support both pxe and ipxe at the same time. However looking at the implementation in ironic I couldn't find the uefi_ipxe_* parameters in stable/train. These parameters were added during the Victoria cycle[1]. [1] https://review.opendev.org/c/openstack/ironic/+/728315 So we can't backport that change in puppet-ironic unless we backport the actual implementation in ironic.
The puppet-ironic backport will require this ironic backport as a prerequesite
The puppet backport is making progress, it has been proposed to ussuri https://review.opendev.org/c/openstack/puppet-ironic/+/802422
I've proposed the puppet change do downstream 16.2
Thanks Steve. Pre-provisioned nodes wouldn't be acceptable to the customer. It would require their Openstack team to have in-depth knowledge of interacting with POWER hardware, and also works against us setting up OSP 16 to help simplify their Day-2 operations. The customer would very likely see this as a step backwards as mixed architecture is an important part of their implementation. -Richard Richard Barrott Principal Technical Account Manager Red Hat Australia rbarrott Ph: 0420578132
this was not considered a locker by the trac team please see https://issues.redhat.com/browse/OSP-10323
Here are the proposed patches for rhos-16.2-patches: https://code.engineering.redhat.com/gerrit/c/ironic/+/290961 https://code.engineering.redhat.com/gerrit/c/puppet-ironic/+/290974 Also the Target Milestone is set back at z1, to match what the exception flag is for.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.2), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:1001