Description of problem: selected one disk of a previous btrfs instance, went to manual partitioning and deleted partitons. used the guided partitioning to propose partitions, kaboom Version-Release number of selected component: anaconda-18.28 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.6-3.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.28 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1134, in newLV : raise ValueError("name already in use") : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 267, in _scheduleVolumes : dev = new_volume(**kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 306, in doAutoPartition : _scheduleVolumes(storage, devs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1861, in _do_autopart : doAutoPartition(self.__storage, self.data) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1893, in on_create_clicked : self._do_autopart() :ValueError: name already in use
Created attachment 642842 [details] File: anaconda-tb
Created attachment 642844 [details] File: product
Created attachment 642846 [details] File: type
Created attachment 642848 [details] File: ifcfg.log
Created attachment 642849 [details] File: storage.log
Created attachment 642850 [details] File: version
Created attachment 642851 [details] File: environ
Created attachment 642852 [details] File: executable
Created attachment 642853 [details] File: anaconda.log
Created attachment 642854 [details] File: syslog
Created attachment 642855 [details] File: hashmarkername
Created attachment 642856 [details] File: packaging.log
Created attachment 642857 [details] File: cmdline_file
Created attachment 642858 [details] File: release
Created attachment 642859 [details] File: program.log
Enhanced steps to reproduce: 0. Enter STORAGE: INSTALLATION DESTINATION 1. Select one DISK 2. Go to MANUAL PARTITIONING 3. Delete the found BTRFS and the prior /boot partitions 4. Use the guide or wizard to propose partitions and 'finish partitioning'
Corrected step #4. Enhanced steps to reproduce: 0. Enter STORAGE: INSTALLATION DESTINATION 1. Select one DISK 2. Go to MANUAL PARTITIONING 3. Delete the found BTRFS and the prior /boot partitions 4. Use the guide or wizard the error happens after clicking the guided partitioning, it is not possible to reach the 'finish partitioning' button.
*** Bug 875497 has been marked as a duplicate of this bug. ***
i selected some disks, went to automatic partitioning and reclaimed space. i only set a btrfs to 'shrink' Package: anaconda-18.29 OS Release: Fedora release 18-Beta-TC9
The check for name already in use in newLV is only checking the LV name when what matters is $vgname-$lvname.
Discussed at 2012-11-29 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-11-29/f18final-blocker-review-1.1.2012-11-29-17.01.log.txt . 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 ...".
pykickstart-1.99.22-1.fc18, anaconda-18.34-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.34-1.fc18
Package pykickstart-1.99.22-1.fc18, anaconda-18.34-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 pykickstart-1.99.22-1.fc18 anaconda-18.34-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.34-1.fc18 then log in and leave karma (feedback).
Reartes, could you please try to reproduce again with this image? http://dl.fedoraproject.org/pub/alt/qa/20121201_f18-smoke2/ It contains the latest anaconda. It should hopefully fix the issue. Thanks.
Package pykickstart-1.99.22-1.fc18, anaconda-18.35-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 pykickstart-1.99.22-1.fc18 anaconda-18.35-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.35-1.fc18 then log in and leave karma (feedback).
pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Reartes, can you verify this is fixed? Please try this image: http://dl.fedoraproject.org/pub/alt/qa/20121205_f18-smoke4/ Thanks.
@Kamil Páral I reproduced the issue first, then tried on the same guest with the smoke4 (netinstall) and there was no error. It looks the issue is fixed. Thanks.
Thank you, Reartes.