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:

In Manual Partitioning screen, when you configure a single mount point by clicking on the icon in the icon pane, and finish the dialog, you still need to click Update Settings for the setting to take effect.

This is highly unintuitive since the button is on the other side of the screen and seemingly not related to the mount point configuration.

An easy way to fix this is to simply update the settings automatically upon clicking Select in the Configure Mount Point dialog.

Here's mockups I did of an idea we had in IRC this morning to rearrange the screen to help alleviate the confusion here:
https://www.redhat.com/archives/anaconda-devel-list/2014-July/msg00046.html

This is just my initial mockup / explanation and is of course subject to the team reviewing it and potential back-and-forth/changes happening during that process.

This is the mockup for the redesing of the Custom partitioning spoke:
http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Move-Device-Selection-Custom-Part/after.2.png

and this is how the proposed patch implements it:
https://vpodzime.fedorapeople.org/new_custom_spoke.webm

Created attachment 961922 [details]
The storage configuration spoke as it is right now

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