Version-Release number of selected component: anaconda-18.16-1.fc18.x86_64 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.16 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/parted/disk.py", line 269, in removePartition : if self.__disk.remove_partition(partition.getPedPartition()): : File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 32, in new : ret = fn(*args, **kwds) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 574, in removeNewPartitions : part.disk.format.partedDisk.removePartition(part.partedPartition) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 758, in doPartitioning : removeNewPartitions(disks, partitions) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 302, in doAutoPartition : doPartitioning(storage) : File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 265, in execute : doAutoPartition(storage, ksdata) : File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1557, in doKickstartStorage : ksdata.autopart.execute(storage, ksdata, instClass) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 380, in _doExecute : doKickstartStorage(self.storage, self.data, self.instclass) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run : threading.Thread.run(self, *args, **kwargs) :PartitionException: Partition is not part of the disk it is being removed from
Created attachment 625775 [details] File: ifcfg.log
Created attachment 625776 [details] File: anaconda-tb
Created attachment 625777 [details] File: environ
Created attachment 625778 [details] File: type
Created attachment 625779 [details] File: storage.log
Created attachment 625780 [details] File: version
Created attachment 625781 [details] File: program.log
Created attachment 625782 [details] File: product
Created attachment 625783 [details] File: anaconda.log
Created attachment 625784 [details] File: hashmarkername
Created attachment 625785 [details] File: cmdline_file
Created attachment 625786 [details] File: release
Created attachment 625787 [details] File: messages
Created attachment 625788 [details] File: other involved packages
i was trying to reproduce another bug, by selecting two disks, going to manual partitionig, then back, selecting one disk,auto partitiong, etc. (exact steps unknow) Package: anaconda-18.16 OS Release: Fedora release 18-Beta-TC4
Is this at all reproducible with anaconda-18.19-1? If so, can someone please attach exact steps to cause it to happen? Thanks.
Created attachment 635025 [details] text-mode installation Similar traceback reproduced when running text-mode installation, tested with anaconda-18.19 Steps to reproduce: 1. run installation in text mode 2. select all (3) disks 3. Use All Space 4. go back to Install Destination 5. deselect second disk 6. Use All Space 8. go back to Install Destination 9. select second and deselect third disk 10. Use All Space 11. traceback
I suspect there is some clean up that was done in the gui storage spoke that I need to duplicate in the text storage spoke. Taking this to look into it.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.