Version-Release number of selected component:
The following was filed automatically by anaconda:
anaconda 22.3-1 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/parted/disk.py", line 269, in removePartition
File "/usr/lib/python2.7/site-packages/parted/decorators.py", line 41, in new
ret = fn(*args, **kwds)
File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 325, in removePartition
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 438, in _removeDevice
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 496, in registerAction
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1298, in destroyDevice
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1708, in _destroy_device
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 121, in decorated
return func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1831, in on_remove_clicked
PartitionException: Attempting to remove a partition that is not owned by any disk.
cmdline: /usr/bin/python /sbin/anaconda
cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-rawhide-i386 quiet
release: Cannot get release name.
Created attachment 927618 [details]
Created attachment 927619 [details]
Created attachment 927620 [details]
Created attachment 927621 [details]
Created attachment 927622 [details]
Created attachment 927623 [details]
Created attachment 927624 [details]
Created attachment 927625 [details]
Created attachment 927626 [details]
Created attachment 927627 [details]
Created attachment 927628 [details]
I managed to work around this:
Initially, I was doing the swap partition last, and it crashed twice when I did. On the third try, I first did the swap partition and then the others and it didn't crash.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
What steps did you take to reach this error? Does it still occur in Fedora 23?
I was just going about the normal installation process - I have a /home partition and things that I remount.
I can't say if the issue still persists - I didn't seem to run into it while installing F23.