Description of problem: Set up a VM with two disks, one containing a single ext4 partition with F19 Beta TC3 DVD iso on it. Run the installer. Go to Installation Source. Pick the ISO file from the second disk as the installation source. Go to Installation Destination. Select both disks as install targets. On Installation Options, go to Reclaim Space. Choose to delete the whole of the second disk. Return to hub. Installation Destination shows up with an orange triangle. Click on it, crash happens. The following was filed automatically by anaconda: anaconda 19.24-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 626, in unmount raise FSError("umount failed") File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 792, in teardown return self.unmount(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 521, in __init__ device.format.teardown() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1169, in destroyDevice self.devicetree.registerAction(ActionDestroyFormat(device)) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 734, in recursiveRemove self.destroyDevice(leaf) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 372, in _scheduleActions self.storage.recursiveRemove(device) FSError: umount failed Version-Release number of selected component: anaconda-19.24-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Beta-TC3\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-301.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Beta-TC3 Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 372, in _scheduleActions self.storage.recursiveRemove(device) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 734, in recursiveRemove self.destroyDevice(leaf) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1169, in destroyDevice self.devicetree.registerAction(ActionDestroyFormat(device)) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 521, in __init__ device.format.teardown() File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 792, in teardown return self.unmount(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 626, in unmount raise FSError("umount failed") FSError: umount failed
Created attachment 745905 [details] File: anaconda.log
Created attachment 745906 [details] File: backtrace
Created attachment 745907 [details] File: environ
Created attachment 745908 [details] File: ifcfg.log
Created attachment 745909 [details] File: lsblk_output
Created attachment 745910 [details] File: nmcli_dev_list
Created attachment 745911 [details] File: packaging.log
Created attachment 745912 [details] File: program.log
Created attachment 745913 [details] File: storage.log
Created attachment 745914 [details] File: syslog
Created attachment 745915 [details] File: anaconda-tb
I think Installation Destination should not allow you to select a disk you've already set as the Installation Source as a target disk.
This is still reproducible with 19.30.5. bcl thought it may be improved by a patch that should help various umount bugs, but apparently not. This is a complex case, though, so it doesn't mean the patch is useless.
Is this issue still reproducable with F21?
For the record, this seems to be fixed with 21 at least. You can't delete the partition. You can 'delete' the disk (which usually sets all partitions on the disk to be deleted), which is a bit weird when the *only* partition on the disk will not in fact be deleted, but that's a very minor cosmetic niggle. changing resolution.