Version-Release number of selected component: anaconda-22.3-1 The following was filed automatically by anaconda: anaconda 22.3-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/shutil.py", line 83, in copyfile with open(dst, 'wb') as fdst: File "/usr/lib64/python2.7/shutil.py", line 119, in copy copyfile(src, dst) File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 876, in copyFileToPath shutil.copy(fileName, destfile) File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 1036, in write_network_config copyFileToPath("/etc/resolv.conf", rootpath, overwrite=flags.livecdInstall) File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1001, in execute network.write_network_config(storage, ksdata, instClass, iutil.getSysroot()) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 90, in doConfiguration ksdata.network.execute(storage, ksdata, 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) IOError: [Errno 2] Adresár alebo súbor neexistuje: '/mnt/sysimage/etc/resolv.conf' Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-rawhide-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.17.0-0.rc1.git0.1.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 929100 [details] File: anaconda-tb
Created attachment 929102 [details] File: anaconda.log
Created attachment 929103 [details] File: environ
Created attachment 929104 [details] File: lsblk_output
Created attachment 929105 [details] File: nmcli_dev_list
Created attachment 929106 [details] File: os_info
Created attachment 929107 [details] File: program.log
Created attachment 929108 [details] File: storage.log
Created attachment 929109 [details] File: syslog
Created attachment 929110 [details] File: ifcfg.log
Created attachment 929111 [details] File: packaging.log
/etc/resolv.conf is a broken symlink into /run/systemd, again.
*** Bug 1132623 has been marked as a duplicate of this bug. ***
(In reply to David Shea from comment #12) > /etc/resolv.conf is a broken symlink into /run/systemd, again. Yes, anaconda should remove not follow the symlink. systemd-216-2 temporarily again has the patch to not create the symlink.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #14) > (In reply to David Shea from comment #12) > > /etc/resolv.conf is a broken symlink into /run/systemd, again. > Yes, anaconda should remove not follow the symlink. Then what's the point of installing the symlink? (NB: I don't actually care about the answer to this) /etc/resolv.conf has been a regular file pointing to regular file things for the last *thirty years!*, you can't just replace vital system files and expect everyone else to clean up the mess you've made. Anaconda is trying to write to /etc/resolv.conf. We can't write to /etc/resolv.conf because someone put something broken in the way. Removing the symlink is a workaround, not a solution.
(In reply to David Shea from comment #15) > (In reply to Zbigniew Jędrzejewski-Szmek from comment #14) > > (In reply to David Shea from comment #12) > > > /etc/resolv.conf is a broken symlink into /run/systemd, again. > > Yes, anaconda should remove not follow the symlink. > > Then what's the point of installing the symlink? The first reason to keep resolv.conf out of /etc is that the contents are variable, and moving it out is a prerequisite for a read-only /etc. A second reason is that there are multiple programs which can provide resolv.conf, e.g. systemd-resolved, NetworkManager, other dhcp clients, etc. Which one is used can then be easily determined by the administrator by setting the symlink. > (NB: I don't actually care > about the answer to this) /etc/resolv.conf has been a regular file pointing > to regular file things for the last *thirty years!*, you can't just replace > vital system files and expect everyone else to clean up the mess you've made. Things change. There are valid technical reasons for the change. > Anaconda is trying to write to /etc/resolv.conf. We can't write to > /etc/resolv.conf because someone put something broken in the way. Removing > the symlink is a workaround, not a solution. There's no reason for anaconda to follow the symlink, no matter if it points to an existing file or not.
*** Bug 1133150 has been marked as a duplicate of this bug. ***
Has anaconda been updated to remove the symlink?
(In reply to Zbigniew Jędrzejewski-Szmek from comment #18) > Has anaconda been updated to remove the symlink? No.
Can we set a time schedule when this will happen then? We're currently patching out this part of upstream functionality, but I don't want to carry the workaround for another release.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Another user experienced a similar problem: Install to Hard Drive with live image fc23 rawhide cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-rawhide-20 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.0-0.rc4.git2.1.fc23.x86_64 other involved packages: python-libs-2.7.9-5.fc22.x86_64 package: anaconda-core-23.4-1.fc23.x86_64 product: Fedora reason: IOError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/resolv.conf' release: Fedora release 23 (Rawhide) version: Rawhide
*** Bug 1211838 has been marked as a duplicate of this bug. ***
I got this on the rawhide install image yesterday.
Another user experienced a similar problem: error occured whist attempting to install fedora rawhide, Fedora-Live-MATE-Compiz-i686-29150429.iso, as guest on Oracle VM Virtualbox version 4.3.26 r98988. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-MATE-i686-rawhide-20 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.1.0-0.rc1.git0.1.fc23.i686 other involved packages: python-libs-2.7.9-10.fc23.i686 package: anaconda-core-23.7-1.fc23.i686 product: Fedora reason: IOError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/resolv.conf' release: Fedora release 23 (Rawhide) version: Rawhide
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.
Anyway, we create the symlink from systemd-resolved when it starts now.