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.

+++ This bug was initially created as a clone of Bug #1144520 +++

Description of problem:
Regardless of whether you provided a ks.cfg containing custom storage or previously visited the custom spoke in the GUI, the initial selection is always "Automatic partitioning" or similar.

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

How reproducible:
Always

Steps to Reproduce:
1. either specify a ks w/ custom storage or visit the custom spoke
2. revisit the storage spoke
3. note the setting of autopart -v- custom

Actual results:
It's always autopart.

Expected results:
It should be whatever was previously specified.

Additional info:

--- Additional comment from David Lehman on 2014-09-19 14:54:02 EDT ---

Already fixed on master.

This is fixed in 7.2 as part of the rebase.