Description of problem: Installing Fedora 22 Cloud Beta to KVM guest with a custom partition. Version-Release number of selected component: anaconda-22.20.11-1 The following was filed automatically by anaconda: anaconda 22.20.11-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 687, in unmount raise FSError("umount failed") File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 896, in teardown return self.unmount() File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 615, in umountFilesystems device.format.teardown() File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 1410, in umountFilesystems self.fsset.umountFilesystems(swapoff=swapoff) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 247, in doInstall storage.umountFilesystems() File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run threading.Thread.run(self, *args, **kwargs) FSError: umount failed Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-1.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 22
Created attachment 1021446 [details] File: anaconda-tb
Created attachment 1021447 [details] File: anaconda.log
Created attachment 1021448 [details] File: environ
Created attachment 1021449 [details] File: lsblk_output
Created attachment 1021450 [details] File: nmcli_dev_list
Created attachment 1021451 [details] File: os_info
Created attachment 1021452 [details] File: program.log
Created attachment 1021453 [details] File: storage.log
Created attachment 1021454 [details] File: syslog
Created attachment 1021455 [details] File: ifcfg.log
ostree was holding a descriptor open on /mnt/sysimage, and it looks like that's been fixed. *** This bug has been marked as a duplicate of bug 1217578 ***
I'm presuming this bug was for the "mainline" or "base" cloud image which doesn't use ostree. Joe, is that correct? Which specific install media did you retrieve?
Indeed this is a dupe, sorry.