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
Created attachment 820987 [details] anaconda.log
Created attachment 820988 [details] program.log
Created attachment 820989 [details] storage.log
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
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)
(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.
(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).
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.
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
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).
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.