Description of problem: Attempting to resize existing lv Version-Release number of selected component: anaconda-22.20.9-1 The following was filed automatically by anaconda: anaconda 22.20.9-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 433, in __init__ raise ValueError("new size is too large") File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 1173, in resizeDevice self.devicetree.registerAction(action_class(device, new_size)) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 778, in _handle_size_change self._storage_playground.resizeDevice(use_dev, use_size) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 128, in decorated return func(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1186, in _save_right_side self._handle_size_change(size, old_size, device) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2647, in on_update_settings_clicked self._save_right_side(self._current_selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/utils.py", line 242, in _run_once_one_arg self._func(*args, **kwargs) ValueError: new size is too large Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22_B-x86_64 quiet dnf.rpm.log: Apr 14 20:10:18 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 22
Created attachment 1014440 [details] File: anaconda-tb
Created attachment 1014441 [details] File: anaconda.log
Created attachment 1014442 [details] File: dnf.log
Created attachment 1014443 [details] File: environ
Created attachment 1014444 [details] File: lsblk_output
Created attachment 1014445 [details] File: nmcli_dev_list
Created attachment 1014446 [details] File: os_info
Created attachment 1014447 [details] File: storage.log
Created attachment 1014448 [details] File: syslog
Created attachment 1014449 [details] File: ifcfg.log
Created attachment 1014450 [details] File: packaging.log
Created attachment 1014451 [details] File: program.log
*** Bug 1040445 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Just tried to reproduce bug 1040413 addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22_B-x86_64 quiet dnf.rpm.log: Apr 23 08:09:06 INFO --- logging initialized --- hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 package: anaconda-22.20.9-1 product: Fedora reason: ValueError: new size is too large release: Cannot get release name. version: 22
Proposed as a Blocker for 22-final by Fedora user lbrabec using the blocker tracking app because: Violation of beta criterion: Custom partitioning When using the custom partitioning flow, the installer must be able to: Reject or disallow invalid disk and volume configurations without crashing. and violation of final criterion: Storage volume resize Any installer mechanism for resizing storage volumes must correctly attempt the requested operation.
*** Bug 1214628 has been marked as a duplicate of this bug. ***
After encountering this in bug 1214628 while using custom partitioning, I had another attempt using the guided partitioning workflow. The "reclaim space" dialog in that workflow uses a bounded slider to handle the resizing request on partitions. Would it be possible to also use that slider in the custom partitioning dialogs?
Discussed at the 2015-04-28 blocker review meeting.[1] Voted as AcceptedBlocker. Violates criterion "When using the custom partitioning flow, the installer must be able to: Reject or disallow invalid disk and volume configurations without crashing." [#15] [1]: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-28/
anaconda team, ping - at first blush this looks like it should be fairly straightforward? it's an accepted blocker for F22 so needs fixing fairly soon, thanks!
I have a patch. I'll send it for review on Monday at latest.
Update image available for testing. Just add the following to your boot command line: inst.updates=https://dlehman.fedorapeople.org/updates/updates-1211746.0.img Please share the results here. Thanks.
When trying to reproduce this without the update image, I hit bug 1040413, not this one. David, how to reproduce this? Can you verify the updates img?
(In reply to David Lehman from comment #21) > Update image available for testing. Just add the following to your boot > command line: > > inst.updates=https://dlehman.fedorapeople.org/updates/updates-1211746.0.img > If I use this updates image, I don't hit the bug no matter what I do, and bug 1222811 seems to be fixed.
(In reply to David Lehman from comment #21) > Update image available for testing. Just add the following to your boot > command line: > > inst.updates=https://dlehman.fedorapeople.org/updates/updates-1211746.0.img > > > Please share the results here. Thanks. Yeah that works. (In reply to Kamil Páral from comment #22) > When trying to reproduce this without the update image, I hit bug 1040413, > not this one. David, how to reproduce this? Can you verify the updates img? Reproduced with the same steps in bug 1040445. Started with an autopart layout but with space free in the VG, attempted to add space to the root LV.
I can reproduce the bug now with the following steps: 1) Boot Fedora 22 Server Final TC4 (I did this in a VM with an 8GB disk) 2) In storage setup, select manual creation 3) Click on the automatic setup link to generate the initial set of partitions 4) Select the / partition and reduce it's size (I used 1 GB) 5) Run the installation (I used the minimal package set for speed) 6) Reboot the VM and boot into the installer again. 7) Go to custom partitioning. Select each of the partitions and mark them to format (which will bring them up to the upper part of the left side) 8) Change the size of the / partition (I increased it by 1GB) Anaconda will crash. Side note: this happened with XFS partitions, which is irrelevant because of the reformatting anyway. I'm going to test the updates.img now.
I can also confirm that the provided updates.img fixes the bug.
anaconda-22.20.13-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/anaconda-22.20.13-1.fc22
Package anaconda-22.20.13-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-22.20.13-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8539/anaconda-22.20.13-1.fc22 then log in and leave karma (feedback).
This particular problem seems to be fixed, but continuing with the installation, I encountered bug 1221247.
anaconda-22.20.13-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.