Description of problem: I started the live install over VNC and first item on screen was that a serious error had occured Version-Release number of selected component: anaconda-22.20.2-1 The following was filed automatically by anaconda: anaconda 22.20.2-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 82, in setup raise PayloadInstallError("Failed to mount the install tree") File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 1219, 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 238, in run threading.Thread.run(self, *args, **kwargs) PayloadInstallError: Failed to mount the install tree Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base --vnc cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-22_A-x86_64 rd.live.check quiet dnf.rpm.log: Mar 13 22:14:16 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-0.rc1.git0.1.fc22.x86_64 product: Fedora" release: Cannot get release name. type: anaconda version: Fedora Potential duplicate: bug 1164577
Created attachment 1001511 [details] File: anaconda-tb
Created attachment 1001512 [details] File: anaconda.log
Created attachment 1001513 [details] File: dnf.log
Created attachment 1001514 [details] File: environ
Created attachment 1001515 [details] File: lsblk_output
Created attachment 1001516 [details] File: nmcli_dev_list
Created attachment 1001517 [details] File: os_info
Created attachment 1001518 [details] File: storage.log
Created attachment 1001519 [details] File: syslog
Created attachment 1001520 [details] File: ifcfg.log
Created attachment 1001521 [details] File: packaging.log
Created attachment 1001522 [details] File: program.log
This was caused by running the installer multiple times, and the behavior in this situation should be better now. *** This bug has been marked as a duplicate of bug 1164577 ***