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 #1144560 +++

Description of problem:
if you do an actual kickstart installation with a ks.cfg that contains a custom storage layout, then try to enter the storage spoke to go view/adjust your layout in the custom spoke, it will try to allocate everything again between the storage and custom spokes, which causes an error, which causes us to reset everything and lose your custom layout.

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

How reproducible:
always

Steps to Reproduce:
1. do a kickstart install with a non-working base repo and custom storage
2. visit the storage spoke, proceed to custom spoke
3.

Actual results:
everything has been reset to on-disk

Expected results:
my custom layout is visible in custom spoke

Additional info:

--- Additional comment from David Lehman on 2014-09-19 14:25:48 EDT ---

Already fixed on master.

It turns out this is only hittable if something about the ks.cfg prevents anaconda from leaving the first hub, which is often the case for me since I often specify a stage1 that has no repodata or packages in the tree.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0312.html