Description of problem: Started Atomic Host install without network connectivity (no DHCP but Ethernet was up). Version-Release number of selected component: anaconda-22.20.13-1 The following was filed automatically by anaconda: anaconda 22.20.13-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 51, in _writeKS with open(path, "w") as f: File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 127, in doConfiguration _writeKS(ksdata) 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) IOError: [Errno 2] No such file or directory: '/mnt/sysimage/ostree/deploy/fedora-atomic/deploy/06a63ecfcf053d1625e9ddf406429eef3c7fe3ecccbe636a54b90175a5899e7d.0/root/anaconda-ks.cfg' 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.4-301.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 22 Potential duplicate: bug 1107679
Created attachment 1058649 [details] File: anaconda-tb
Created attachment 1058650 [details] File: anaconda.log
Created attachment 1058651 [details] File: environ
Created attachment 1058652 [details] File: lsblk_output
Created attachment 1058653 [details] File: nmcli_dev_list
Created attachment 1058654 [details] File: os_info
Created attachment 1058655 [details] File: storage.log
Created attachment 1058656 [details] File: syslog
Created attachment 1058657 [details] File: ifcfg.log
Created attachment 1058658 [details] File: program.log
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.