This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2149862 - [RFE] Image Builder: advanced partitioning mode
Summary: [RFE] Image Builder: advanced partitioning mode
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: osbuild-composer
Version: 8.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Image Builder team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-01 08:44 UTC by Christophe Besson
Modified: 2023-09-18 13:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 13:26:12 UTC
Type: Story
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4617 0 None Migrated None 2023-09-18 13:26:05 UTC
Red Hat Issue Tracker RHELPLAN-141050 0 None None None 2022-12-01 15:19:53 UTC
Red Hat Knowledge Base (Solution) 6989033 0 None None None 2022-12-05 12:05:51 UTC

Description Christophe Besson 2022-12-01 08:44:54 UTC 
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:
# 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:
Comment 5 RHEL Program Management 2023-09-18 13:23:56 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6 RHEL Program Management 2023-09-18 13:26:12 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.