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:
As discussed in Brno, kickstart is recommended way to install on custom partition layout e.g. when not possible using Anaconda.
Without working '--useexisting' options to volgroup and logvol this is impossible.

Version-Release number of selected component (if applicable):
anaconda-19.23-1

How reproducible:
100%

Steps to Reproduce:
1. try to use existing VG or LV (does not matter whether created in %pre which does not work anyway or prepared in advance) in kickstart.
  
Actual results:
Backtrace saying: "volgroup must be given a list of partitions".

Expected results:
Installation using prepared VG.

Additional info:

Now it works with PV+VG prepared in advance. PEBKAC: clearpart in my ks to blame.

However I am still unable to create PVs/VGs/LVs in %pre.

Is it supposed/known to work? (Do I need to spend more time debugging my env?)

Closing per comment #2.  We do not guarantee things work via %pre.  That is a preinstall script area for users, but something not working in %pre does not indicate a bug in the installer.  It almost always is an invalid, incorrect, or incomplete set of commands you're running in %pre.