Version-Release number of selected component: anaconda-core-22.11-1.fc22.x86_64 The following was filed automatically by anaconda: anaconda 22.11-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 81, in setup raise PayloadInstallError("Failed to mount the install tree") File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 1216, in _runThread payload.setup(storage, instClass) 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 227, in run threading.Thread.run(self, *args, **kwargs) PayloadInstallError: Failed to mount the install tree Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-rawhide-20 ro rd.live.image quiet rhgb executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.18.0-0.rc7.git1.1.fc22.x86_64 other involved packages: python-libs-2.7.8-9.fc22.x86_64 product: Fedora" release: Fedora release 22 (Rawhide) type: anaconda version: Fedora Potential duplicate: bug 1164577
Created attachment 964989 [details] File: anaconda-tb
Created attachment 964990 [details] File: anaconda.log
Created attachment 964991 [details] File: environ
Created attachment 964992 [details] File: journalctl
Created attachment 964993 [details] File: lsblk_output
Created attachment 964994 [details] File: nmcli_dev_list
Created attachment 964995 [details] File: os_info
Created attachment 964996 [details] File: program.log
Created attachment 964997 [details] File: storage.log
Created attachment 964998 [details] File: ifcfg.log
The underlying problem here is bug 1167036. The traceback you are hitting then is a result of anaconda not cleaning up after that first bug, and then you running liveinst again against a system that's not been cleaned up. Duping! *** This bug has been marked as a duplicate of bug 1167036 ***