Bug 1027714

Summary: Re-using LVM partitions makes them non-resizable in certain cases
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: python-blivetAssignee: David Lehman <dlehman>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: amulhern, anaconda-maint-list, awilliam, bcl, dlehman, g.kaviyarasu, jonathan, robatino, satellitgo, vanmeeuwen+fedora
Target Milestone: ---Keywords: CommonBugs
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: https://fedoraproject.org/wiki/Common_F20_bugs#resize-bugs RejectedBlocker
Fixed In Version: pykickstart-1.99.46-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1029633 (view as bug list) Environment:
Last Closed: 2013-11-24 03:59:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1029633    
Attachments:
Description Flags
bug demonstration video
none
anaconda.log
none
program.log
none
storage.log none

Description Kamil Páral 2013-11-07 10:27:47 UTC
Created attachment 820986 [details]
bug demonstration video

Description of problem:
I had a previous F20 LVM installation. I wanted to reuse swap, /boot and /, and delete /home. I achieved that, but I could not enlarge / to occupy space reclaimed by deleting /home. Anaconda claims that the partition is not resizable.

Please see the video.

Also please notice that the free space counter is totally off, not reflecting deleted partitions.

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

How reproducible:
always

Steps to Reproduce:
1. create /boot as a standard partition and swap, / and /home on LVM
2. install, then reboot again into the installer
3. reuse swap and /boot
4. delete /home
5. try to reuse / and enlarge it to occupy space reclaimed by deleting /home
6. see that the partition refuses to be enlarged

Comment 1 Kamil Páral 2013-11-07 10:28:19 UTC
Created attachment 820987 [details]
anaconda.log

Comment 2 Kamil Páral 2013-11-07 10:28:42 UTC
Created attachment 820988 [details]
program.log

Comment 3 Kamil Páral 2013-11-07 10:28:50 UTC
Created attachment 820989 [details]
storage.log

Comment 4 Kamil Páral 2013-11-07 11:01:59 UTC
I guess this is quite inconvenient if you want to reuse some partitions and just enlarge them. It might violate:
"Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. "
https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Storage_volume_resize

Comment 5 satellitgo 2013-11-07 11:30:22 UTC
followed:
Steps to Reproduce:
1. create /boot as a standard partition and swap, / and /home on LVM
2. install, then reboot again into the installer
-On existing default ext4/LVM install on USB HD:
-Custom
3. reuse swap and /boot
4. delete /home
5. try to reuse / and enlarge it to occupy space reclaimed by deleting /home
-manually entered larger value for / and applied it
-[back]
6. see that the partition refuses to be enlarged
-error message in disk spoke on main hub
7. Re-entered disk and did delete all
8. Continued installing sugar-desktop
(anaconda 20.25.6-1 did not crash)

Comment 6 Kamil Páral 2013-11-07 16:45:23 UTC
(In reply to satellit from comment #5)
> 6. see that the partition refuses to be enlarged
> -error message in disk spoke on main hub

In this step you diverted from my reproducer. You have to tell us what error you saw. I saw no error. Maybe you tried to enlarge it too much (larger than available space)?

> 7. Re-entered disk and did delete all

This is the reason why you haven't received a crash afterwards.

Comment 7 Kamil Páral 2013-11-07 17:43:00 UTC
(In reply to Kamil Páral from comment #6)
> > 7. Re-entered disk and did delete all
> 
> This is the reason why you haven't received a crash afterwards.

I take that back. This bug is not about crashing, just about uneditable fields. (I actually did not try to go further).

Comment 8 Adam Williamson 2013-11-13 19:53:47 UTC
Discussed at 2013-11-13 blocker review meeting - http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-13/f20-final-blocker-review-1.2013-11-13-17.01.log.txt . Rejected as a blocker as this does not appear to violate any criteria: it's just a case where anaconda refuses to offer an operation that perhaps it ought to, but no major fail occurs.

Comment 9 Fedora Update System 2013-11-16 02:18:35 UTC
anaconda-20.25.8-1.fc20, pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pykickstart-1.99.46-1.fc20,python-blivet-0.23.5-1.fc20,anaconda-20.25.8-1.fc20

Comment 10 Fedora Update System 2013-11-17 07:03:39 UTC
Package anaconda-20.25.8-1.fc20, pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.25.8-1.fc20 pykickstart-1.99.46-1.fc20 python-blivet-0.23.5-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-21553/pykickstart-1.99.46-1.fc20,python-blivet-0.23.5-1.fc20,anaconda-20.25.8-1.fc20
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2013-11-24 03:59:21 UTC
pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20, anaconda-20.25.9-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.