Description of problem:
Customer would like to be able to customize the partition layout according to their standards. They build AMI images for x86_64 as well as aarch64 and they want to have the LVM on the last physical partition (and /boot as 2nd).

Using Image Builder, /boot is always the latest (3rd or 4th) and they'd like to know why (is it a deliberate choice for a technical reason?).

Customer also argues "this doesn't line up and the results from Image Builder should match the public RH AMI":
NAME FSTYPE LABEL UUID MOUNTPOINT
nvme0n1
├─nvme0n1p1 vfat 7B77-95E7 /boot/efi
├─nvme0n1p2 xfs 4df66650-964a-4178-b95f-97717f4059a5 /boot
└─nvme0n1p3 xfs root b2de97b2-9d86-42ff-94f2-ed2c0bc1d661 /

Customer also insists on the need to have separate LVs for /var/log and /var/log/audit, but this request has already been mentioned in rhbz#2127960.

Version-Release number of selected component (if applicable):
osbuild-composer-62-3.el8_7

How reproducible:
Always

Steps to Reproduce:
Build an image and observe /boot is always the last partition.

Actual results:

1. fdisk -l image.raw
   Disk image.raw: 13 GiB, 13962838016 bytes, 27271168 sectors
   Units: sectors of 1 * 512 = 512 bytes
   Sector size (logical/physical): 512 bytes / 512 bytes
   I/O size (minimum/optimal): 512 bytes / 512 bytes
   Disklabel type: gpt
   Disk identifier: D209C89E-EA5E-4FBD-B161-B461CCE297E0

Device Start End Sectors Size Type
image.raw1 2048 4095 2048 1M BIOS boot
image.raw2 2101248 27271134 25169887 12G Linux LVM
image.raw3 4096 2101247 2097152 1G Linux extended boot

Expected results:
LVM on the last physical partition.

Additional info:

Currently supported only through unpacking the image (https://access.redhat.com/solutions/6989033)