Bug 1203482 - etc/resolv.conf couldn't find thus anaconda crashes
Summary: etc/resolv.conf couldn't find thus anaconda crashes
Keywords:
Status: CLOSED DUPLICATE of bug 1197204
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 23
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-19 00:45 UTC by Ömer Fadıl Usta
Modified: 2015-07-23 19:12 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-07-23 19:12:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1197204 0 unspecified CLOSED /etc/resolv.conf should be managed by the network daemon not systemd 2021-02-22 00:41:40 UTC

Internal Links: 1197204

Description Ömer Fadıl Usta 2015-03-19 00:45:57 UTC
Description of problem:
When i start with a latest rawhide fedora-workstation livecd( x86_64 ) and
try to install fedora anaconda crashes after a while later.

In anaconda.log : 

06:20:13,274 INFO anaconda: Not doing 'copy /etc/resolv.conf to sysroot' in live installation

Then after a few minutes i'm getting a crash  and log says that :

06:24:30,169 CRIT anaconda: Traceback (most recent call last):

  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 238, in run
    threading.Thread.run(self, *args, **kwargs)

  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/install.py", line 93, in doConfiguration
    ksdata.network.execute(storage, ksdata, instClass)

  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1080, in execute
    network.write_network_config(storage, ksdata, instClass, iutil.getSysroot())

  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 1089, in write_network_config
    copyFileToPath("/etc/resolv.conf", rootpath, overwrite=flags.livecdInstall)

  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 920, in copyFileToPath
    shutil.copy(fileName, destfile)

  File "/usr/lib64/python2.7/shutil.py", line 119, in copy
    copyfile(src, dst)

  File "/usr/lib64/python2.7/shutil.py", line 83, in copyfile
    with open(dst, 'wb') as fdst:

IOError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/resolv.conf'

Comment 1 Ömer Fadıl Usta 2015-03-19 00:52:15 UTC
[liveuser@localhost ~]$ cat /mnt/sysimage/etc/resolv.conf 
cat: /mnt/sysimage/etc/resolv.conf: No such file or directory

[liveuser@localhost ~]$ ls -la /mnt/sysimage/etc/resolv.conf 
lrwxrwxrwx. 1 root root 34 Mar 18 05:22 /mnt/sysimage/etc/resolv.conf -> ../run/systemd/resolve/resolv.conf

Comment 2 Adam Williamson (Red Hat non-Fedora) 2015-03-19 03:56:24 UTC
Doesn't anaconda give you the option to report the crash through the crash reporter? That would provide all the required information.

Comment 3 Ömer Fadıl Usta 2015-03-19 04:28:18 UTC
(In reply to awilliam from comment #2)
> Doesn't anaconda give you the option to report the crash through the crash
> reporter? That would provide all the required information.

Unfortunately the whole gui became frozen and even i couldn't click
the show more info in CrashReporter.

I have made this workaround and i can finish installation without any problem :
Before i start anaconda:
sudo mkdir /run/system.d/resolve
sudo cp /etc/resolv.conf /run/system.d/resolve/resolv.conf
And anaconda didn't give any error for installing system
and i can boot my installed system without any problem

Comment 4 Jan Kurik 2015-07-15 14:23:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 5 David Shea 2015-07-23 19:12:39 UTC

*** This bug has been marked as a duplicate of bug 1197204 ***


Note You need to log in before you can comment on or make changes to this bug.