Description of problem: Installing ostree payload from local compose of fedora-atomic in VM. Version-Release number of selected component: anaconda-21.39-1 The following was filed automatically by anaconda: anaconda 21.39-1 exception report Traceback (most recent call first): File "/tmp/updates/pyanaconda/install.py", line 47, in _writeKS with open(path, "w") as f: File "/tmp/updates/pyanaconda/install.py", line 116, in doConfiguration _writeKS(ksdata) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/tmp/updates/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) IOError: [Errno 2] No such file or directory: '/mnt/sysimage/ostree/deploy/fedora-atomic/deploy/60506ba30bdd1a5070dda106492f4bacd2cf947026f615343e78437608947c71.0/root/anaconda-ks.cfg' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=test/rv/raw20140604/initrd.img root=live:http://10.34.39.2/trees/rv/raw20140604/squashfs.img lang=en_US.UTF-8 keymap=us inst.ks=http://10.34.39.2/ks/rv/ks.ostree.cfg updates=http://10.34.39.2/ks/rv/updates.ostree-rootmnt.img BOOT_IMAGE=test/rv/raw20140604/vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.15.0-0.rc8.git1.2.fc21.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 907219 [details] File: anaconda-tb
Created attachment 907220 [details] File: anaconda.log
Created attachment 907221 [details] File: environ
Created attachment 907222 [details] File: ks.cfg
Created attachment 907223 [details] File: lsblk_output
Created attachment 907224 [details] File: nmcli_dev_list
Created attachment 907225 [details] File: os_info
Created attachment 907226 [details] File: program.log
Created attachment 907227 [details] File: storage.log
Created attachment 907229 [details] File: syslog
Created attachment 907230 [details] File: ifcfg.log
Can this one be closed for the same reasons as bug 1107667?
(In reply to Chris Lumens from comment #12) > Can this one be closed for the same reasons as bug 1107667? I've just checked that the case works ok for me with F21 Beta TC2, so closing.