16.2 documented creating custom overcloud whole-disk images where the customer could build their own block device layout: https://docs.redhat.com/it/documentation/red_hat_openstack_platform/16.2/html/director_installation_and_usage/assembly_creating-whole-disk-images#assembly_creating-whole-disk-images This was not documented for 17.x on the assumption that the default whole-disk image will meet all customers needs. This has not been the case, multiple customers have requested custom block device layouts. The old approach will no longer work because we now provide the yum repo files from outside the build, so a new approach needs to be documented, which may require some development
I'm moving this back to ON_DEV so that the changes can be reworked on upstream diskimage-builder. This is because this change will be part of the fix for bz 2308366. 2308366 will track adding 4k block device support to diskimage-builder, and this change will track rebuilding an existing overcloud image with block device changes. Increasing the priority and severity to match bz 2308366.
Removing the block-device-yaml script as a requirement of this change being complete. It can be attached to the knowledge base article instead.
All required changes are in diskimage-builder-3.31.1-17.1.20240905210750.0576fad.el9ost which is in compose RHOS-17.1-RHEL-9-20241014.n.1
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 (RHOSP 17.1.4 bug fix and 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/RHBA-2024:9974