Description of problem: 16.2 deployment failed for ironic in overcloud CREATE_FAILED ResourceInError: resources.NovaCompute: Went to status ERROR due to "Message: Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance bddad038-d3f1-4552-9416-d6563d54fa10., Code: 500" Version-Release number of selected component (if applicable): 16.2 How reproducible: everytime Steps to Reproduce: 1. deploy the Overcloud with ironic in overcloud enabled 2. 3. Actual results: OC is failing Expected results: OC should pass Additional info:
grub2 has the change which forbids it being installed to the UEFI boot path in rhel-8.4. So we need to update the documentation that UEFI boot with partition images is not supported. Section 7.2[1] needs to be updated to make it clear that if UEFI boot is enabled they will need to follow the instructions in Chapter 24[2] to build their own whole-disk image. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/director_installation_and_usage/index#setting-uefi-boot-mode [2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/director_installation_and_usage/index#creating-whole-disk-images
I'm going to look at overcloud-full preinstalling the shim and signed grub, and IPA checking for efi paths before deciding whether to run grub2-install and where to place grub.cfg
I just deployed a partition image overcloud-full using master IPA, and it looks like the _preserve_efi_assets path leads to a successful deployment because grub2-install is not run. _preserve_efi_assets was backported to ussuri IPA in the last backport push, so in theory it is a single backport to bring this to train. I think doing this will fix this CI job and unblock us for 16.2. With images that have a populated /boot/efi the only remaining case which results in a grub2-install call is whole-disk+softraid. Train IPA doesn't support softraid at all so unless we're going to start supporting this I think nothing needs to be backported for this scenario.
Blocker+ flag given.
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement advisory), 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/RHEA-2021:3483