Created attachment 835233 [details] bug demonstration video Description of problem: This is a fork of bug 1027947. Several bugs have been identified in it, this is one of them. It's not possible to select an existing logical volume, resize it multiple times, and then change the size back to original value. The size is instead reset to second-to-last value, which is very confusing. You can reset to original size only if you perform a single resize (the first part of the video). Once you perform multiple resizes, you're out of luck. Version-Release number of selected component (if applicable): anaconda 20.25.14 How reproducible: always Steps to Reproduce: 1. boot installer with an existing installation on disk (at least one LV partition) 2. enter custom partitioning 3. select an existing LV partition (e.g. /) and change its size (e.g. from 8GB to 7GB). Click Update Settings. 4. try to change the size back to 8GB, it works. 5. now resize it to two different values, e.g. 5 and 4 GB. 6. try to revert it back to 8 GB, you no longer can. the value is reset to second-to-last value.
Created attachment 835234 [details] anaconda.log
Created attachment 835235 [details] program.log
Created attachment 835236 [details] storage.log
Created attachment 835237 [details] syslog
Proposing a Final blocker: "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 In this case, you cannot really cancel a previously requested (double) resize, unless you reset all your changes completely (that is, however, an available workaround).
Discussed in 2013-12-11 Blocker Review Meeting [1]. Voted as an RejectedBlocker. This is inconvenient, but can be easily worked around by hitting Reset All. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-11/
Does this still occur in F21 or F22?
Reproducing this bug resulted in crash, see bug 1211746.
(In reply to Lukas Brabec from comment #8) > Reproducing this bug resulted in crash, see bug 1211746. I forgot to mention, I used Fedora 22 Beta RC3
Let's renew the needinfo once bug 1211746 is fixed.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This seems to work properly in F22.