Description of problem: I resized existing logical volume to 100GB and it didn't fail although the disk is only 20GB. Then I resized it again to 100TB and it crashed with: Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 207, in _setTargetSize raise ValueError("invalid target size request") File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 589, in __init__ self.device.format.targetSize = newsize File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1250, in resizeDevice self.devicetree.registerAction(action_class(device, new_size)) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1454, in _save_right_side self.__storage.resizeDevice(device, size) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2802, in on_apply_clicked self._save_right_side(self._current_selector) ValueError: invalid target size request Version-Release number of selected component (if applicable): anaconda 20.25.6-1 python-blivet 0.23.4-1 Fedora 20 Beta RC5 How reproducible: Always Actual results: Crash Expected results: Invalid operation is handled properly
Created attachment 821495 [details] anaconda.log
Created attachment 821496 [details] anaconda-tb-Sctp28
Created attachment 821497 [details] storage.log
Proposing as a final blocker, per beta criterion: ""Custom partitioning: Reject or disallow invalid disk and volume configurations without crashing.", with resize issues acceptable as Final blocker.
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 . Accepted as a blocker per criterion cited in comment #4, with the note that resize operations are 'blocking' for Final (we need to clarify the criteria to explain why this is Final not Beta blocker).
Status reviewed at 2013-11-20 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-20/f20-blocker-review.2013-11-20-17.00.log.txt . This bug seems to be clearly defined and reproducible and is now just waiting in the queue to be fixed by anaconda devs.
Is this still reproducible with F20 TC3?
Can't reproduce it with F20 Final TC3.
In that case we can close this, anaconda 20.25.12 is stable.