Bug 629301 - Graphical install won't allow mount points to be assigned manually
Summary: Graphical install won't allow mount points to be assigned manually
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 630140 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-01 14:34 UTC by Phil Clayton
Modified: 2010-09-29 22:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-29 22:04:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Phil Clayton 2010-09-01 14:34:43 UTC
Description of problem
----------------------

When editing the partition table during installation, it is not possible to assign mount points to existing partitions that are not to be formatted.

I have tried numerous configurations and have narrowed this down to

 ** logical volumes under LVM that are encrypted. **

However, I did not have an encrypted non-LVM partition to try with, so

 ** it is possible that it simply affects encrypted partitions. **

The issue occurs for both i386 and x86_64.


Version-Release number of selected component (if applicable)
------------------------------------------------------------

13.42 (as supplied on F13 DVD ISO).


How reproducible
----------------

Every time.


Steps to Reproduce
------------------

It is possible to test this on any machine with an existing Fedora/Linux OS without affecting anything: it is not necessary to go beyond the 'information gathering' stages of the install process.

1. With an existing Fedora installation present, start F13 installation.
   Any install process will probably exhibit this: I tried both
     - local install from F13 DVD and
     - PXE boot with remote install.img

2. Go through the usual installation, along the way selecting
     - 'Basic Storage Devices'
     - 'Fresh Installation'
     - 'Create Custom Layout'

3. You are presented with the partition table.  There are no mount points defined.  Select the volume group to add mount points in.  Click 'Edit'.

4. 'Edit LVM Volume Group' dialog.  There are no mount points defined in the table of logical volumes.  Select the logical volume to assign a mount point to, e.g. lv_home.  Click 'Edit'.

5. 'Edit Logical Volume' dialog.  In the 'Mount Point' drop-down box, select e.g. '/home'.  Ensure that 'Format as' is _unticked_.  Click 'OK'.


Actual results
--------------

In the table of logical volumes, the specified mount point '/home' has not appeared for the logical volume.


Expected results
----------------

In the table of logical volumes, the specified mount point '/home' appears along side the logical volume.


Additional info
---------------

1. When clicking 'OK' in 'Edit LVM Volume Group' dialog, the following appears in terminal 5 (Ctrl+Alt+F5):

Device does not exist.
Command failed
Device does not exist.
Command failed


2. If you repeat step 4 and 5 but tick 'Format as', then you get the expected result.  However, subsequent attempts to untick the 'Format as' option are similarly ignored, so this is not a workaround.

Comment 1 Phil Clayton 2010-09-01 14:39:28 UTC
I tried using f14-Alpha so see if this was fixed but was thwarted by this issue:
https://bugzilla.kernel.org/show_bug.cgi?id=16228
(The suggested workaround 'pci=nocrs' stuffs the drivers and no LVM shows up at all!)

Comment 2 Phil Clayton 2010-09-06 19:41:40 UTC
It is possible that
https://bugzilla.redhat.com/show_bug.cgi?id=630140
is a duplicate.

Note: even though all my test machines had Windows partitions, I was able to assign a mount point for an unencrypted non-LVM partition.

Comment 3 Chris Lumens 2010-09-29 19:35:01 UTC
*** Bug 630140 has been marked as a duplicate of this bug. ***

Comment 4 David Lehman 2010-09-29 22:04:25 UTC
This was fixed in anaconda-14.6-1, so F14 will all include the fix. You are correct, by the way: it only affects encrypted LVs.


Note You need to log in before you can comment on or make changes to this bug.