Bug 484985

Summary: Not possible to alter pre-created LV
Product: [Fedora] Fedora Reporter: Matthew Booth <mbooth>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 11CC: anaconda-maint-list, ask, giallu, jgranado, matthias
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-25 15:39:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew Booth 2009-02-10 23:21:46 UTC
Description of problem:
When trying to edit an existing LV, disk druid appears to lose track of the LV's mount point. On trying to save the edit, you get the error message:

The mount point <Not Applicable> is invalid. Mount points must start with '/' and cannot end with '/', and must contain printable characters and no spaces.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a default layout, and choose to edit it
2. Reduce the size of the swap LV to make some space
3. Select root LV and click Edit
4. Increase the size to maximum and try to save
  
Actual results:
'Mount point' is greyed out when editing. Receive above error when trying to save.

Expected results:
LV size is modified.

Additional info:

Comment 1 Matthew Booth 2009-02-10 23:22:51 UTC
Changing component to anaconda. Previous was a fat finger.

Comment 2 Gianluca Sforna 2009-02-26 08:31:26 UTC
Just reproduced this.

A workaround is to change the file system type to ext2 then back to the default ext3

Comment 3 Joel Andres Granados 2009-04-08 12:45:19 UTC
(In reply to comment #2)
> Just reproduced this.
> 
> A workaround is to change the file system type to ext2 then back to the default
> ext3  
What anaconda version is this?

I just tested with anaconda git and I did not see this issue.

Comment 4 Bug Zapper 2009-06-09 11:15:54 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping