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.

Description of problem:
Anaconda should use liblvm and libcryptsetup to determine the data area start location for any volumes it will create.

liblvm must provide access to what a particular PV's pe_start will be (bug 623808).

libcryptsetup must provide access to what a particular LUKS device's 'Payload offset' will be.

Additional info:
improving anaconda in this manner will enable more comprehensive "I/O topology awareness" at install time.

Do you have a pointer to documentation for using those libraries?

anaconda changes are blocked by upstream acceptance of the as-yet-to-be-completed work described in bug #623808.  Once those are done, we can work on changing anaconda.

Since bug #623808 is currently in ON_QA for 6.2 and the devel freeze is 4 business days away, I'm moving this bug to 6.3.

Anaconda is a python application. Until/unless liblvm provides python bindings this is a non-starter.

Based on comment #7 and where things stand right now with liblvm, I really don't see this happening in the 6.3 timeframe.  Rather than carry this forward forever, I'm going to set devel_ack-.

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Fair enough... but be aware that dropping this may lead to misaligned root volumes in the future.

liblvm and libcryptsetup were thought to be a means to an end for fixing the general issue of making anaconda "I/O topology aware".  That they have been deemed inadequate doesn't change the fact that anaconda is lacking said awareness.