Description of problem: Anaconda 18.23, in partitioning segment: Highlighed existing partition and clicked on gears icon. Version-Release number of selected component: anaconda-18.23 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.5-2.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.23 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 355, in __init__ : raise ValueError("new size same as old size") : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1196, in resizeDevice : self.devicetree.registerAction(action_class(device, new_size)) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1169, in _save_right_side : self.__storage.resizeDevice(device, size) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1929, in on_selector_clicked : self._save_right_side(self._current_selector) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 195, in _onSelectorClicked : cb(selector) :ValueError: new size same as old size
Created attachment 636933 [details] File: anaconda-tb
Created attachment 636934 [details] File: product
Created attachment 636935 [details] File: type
Created attachment 636936 [details] File: ifcfg.log
Created attachment 636937 [details] File: storage.log
Created attachment 636938 [details] File: version
Created attachment 636939 [details] File: environ
Created attachment 636940 [details] File: executable
Created attachment 636941 [details] File: anaconda.log
Created attachment 636942 [details] File: syslog
Created attachment 636943 [details] File: hashmarkername
Created attachment 636944 [details] File: packaging.log
Created attachment 636945 [details] File: cmdline_file
Created attachment 636946 [details] File: release
Created attachment 636947 [details] File: program.log
Anaconda 18,23: In "Manual Partitioning", clicked on name of existing partition. Package: anaconda-18.23 OS Release: Fedora release 18
I chose to review/modify partition layout myself. I then selected an existing /boot partition from a rhel6 install (that install was to partitions, no lvm involved). It was when I made this selection that the unknown error dialog appeared. Package: anaconda-18.23 OS Release: Fedora release 18
UEFI boot full-install DVD. Custom install to GPT disk that was pre-partitioned and formatted by gparted LiveCD: 50MiB fat16 EFI System Partition (boot flag), 500MiB ext4 /boot, 15GiB / (root), 4GiB swap. Click on '+' to expand "Unknown", click on "EFI System Partition". Traceback. Package: anaconda-18.23 OS Release: Fedora release 18
Yeah, trivially reproducible. Sigh.
With the number of people hitting this and how simple it sounds to reproduce, looks blocker-y. Technically 18.23 isn't in stable yet, but we should track this as we obviously need to ship something post-18.22.
*** Bug 868698 has been marked as a duplicate of this bug. ***
whoops, nominated for final not beta by mistake.
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.24-1.fc18
Package anaconda-18.24-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.24-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17543/anaconda-18.24-1.fc18 then log in and leave karma (feedback).
Discussed at 2012-11-05 QA meeting acting as a blocker review meeting. Accepted as a blocker per criterion "The installer's custom partitioning mode must be capable of the following ... Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types."
If you need testing, just point me to an install image that has the new anaconda and I'd be happy to give it a try. Thanks!
Jeffrey: https://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC7/ has 18.24. Thanks! Can anyone else who could reproduce this please test with 18.24 and confirm that it's fixed? Thanks!
booted a guest with a preexisting f18, selected the disk and entered manual partitioning selected the /, changed it size to 500000 then to 0 and then back to 500000 Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7
Burned a TC7 CD his morning. Booted it on a box with 3 physical drives. Deleted the existing partitions via the do-it-myself Reclaim Space option. Went to Manual Partition screen where, correctly, no partitions were visible. Clicked on "Automatic", which created /, /Boot, /Home, and swap. Resized /Home, /, and swap, then created a few other partitions. Everything successful. The partitioning made efficient and logical use of the drives, but, except for /Boot and / on the designated boot drive, I didn't see a way to identify or control which partitions went on which drives.
wagerrard: click the 'gears' button next to the + and - buttons, and you get a dialog that lets you pick what disk the partition goes on.
bcl, comment #28 indicates reartes managed to hit this even with 18.24. does that indicate a problem with the fix, or is his a corner case that wasn't covered? how worried are we?
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.25-1.fc18
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18
David, can you take a look at this, re comment #31? Is the fix incomplete? how bad is it that this can still be reproduced with the method described in #28?
(In reply to comment #28) > booted a guest with a preexisting f18, selected the disk and entered manual > partitioning > selected the /, changed it size to 500000 then to 0 and then back to 500000 > > > Package: anaconda-18.24 > OS Release: Fedora release 18-Beta-TC7 Please open a new bug report including all logs. Thanks.
as wagerrard reports the initial reproducer of this is fixed, and dlehman considers the comment #28 reproducer a separate bug, setting VERIFIED.
anaconda-18.27-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.27-1.fc18
18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken). Subsequent dupes of this are likely to be a different bug (see comment #35).
I finally got around to testing this and it worked fine for me.
Thanks for the confirmation, Jeffrey.