Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1538638 - /etc/resolv.conf not created
Summary: /etc/resolv.conf not created
Keywords:
Status: CLOSED DUPLICATE of bug 1537977
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2018-01-25 13:57 UTC by Dan Horák
Modified: 2018-02-22 10:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-05 07:36:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
anaconda.log (35.86 KB, text/plain)
2018-01-30 13:58 UTC, Dan Horák 		no flags Details
anaconda.log (14.70 KB, text/plain)
2018-01-30 14:12 UTC, Dan Horák 		no flags Details
ifcfg.log (1.51 KB, text/plain)
2018-01-30 14:13 UTC, Dan Horák 		no flags Details
syslog (219.30 KB, text/plain)
2018-01-30 14:13 UTC, Dan Horák 		no flags Details
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1493479 0 high CLOSED Enable fedora-* services from initscripts by default 2022-05-16 11:32:56 UTC

Internal Links: 1493479

Description Dan Horák 2018-01-25 13:57:49 UTC 
When installing rawhide (20180123) on s390x with network details set on the kernel command line (via dracut), the /etc/resolv.conf file isn't created and installation source (repo URL) can't be set. This is when install.img/anaconda runs, name resolution works fine in the initrd (it downloads install.img).

The parameter file content is
ro ramdisk_size=40000 cio_ignore=all,!condev rd.dasd=200-207 vnc
ip=1.2.3.4::1.2.3.255:24:foo.bar.com:enc800:none
rd.znet=qeth,0.0.0800,0.0.0801,0.0.0802,layer2=0,portno=0
repo=https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180123.
n.1/compose/Everything/s390x/os/
root=live:https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-2018
0123.n.1/compose/Everything/s390x/os/images/install.img
nameserver=10.9.8.7


Version-Release number of selected component (if applicable):
anaconda 28.18-1.fc28


How reproducible:
100%
Comment 1 Dan Horák 2018-01-25 14:12:17 UTC 
[anaconda root@devel7 tmp]# nmcli dev show
GENERAL.DEVICE:                         enc800
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         02:00:00:00:00:BD
GENERAL.MTU:                            1492
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     enc800
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
WIRED-PROPERTIES.S390-SUBCHANNELS[1]:   0.0.0800
WIRED-PROPERTIES.S390-SUBCHANNELS[2]:   0.0.0801
WIRED-PROPERTIES.S390-SUBCHANNELS[3]:   0.0.0802
IP4.ADDRESS[1]:                         1.2.3.4/21
IP4.GATEWAY:                            1.2.3.255.254
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 10.16.111.254, mt = 0
IP4.ROUTE[2]:                           dst = 1.2.3.0/24, nh = 0.0.0.0, mt = 0
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ff00::/8, nh = ::, mt = 256, table=255

seems NM isn't aware of the DNS server set on the kernel command line
Comment 2 Radek Vykydal 2018-01-29 08:27:31 UTC 
May be related to bug #1537977.

Could you please attach these logs?
/tmp/anaconda.log
/tmp/ifcfg.log
/tmp/syslog
Thank you.
Comment 3 Dan Horák 2018-01-30 13:58:19 UTC 
Created attachment 1388409 [details]
anaconda.log
Comment 4 Dan Horák 2018-01-30 14:12:58 UTC 
Created attachment 1388415 [details]
anaconda.log
Comment 5 Dan Horák 2018-01-30 14:13:03 UTC 
Created attachment 1388416 [details]
ifcfg.log
Comment 6 Dan Horák 2018-01-30 14:13:08 UTC 
Created attachment 1388417 [details]
syslog
Comment 7 Dan Horák 2018-01-30 14:14:51 UTC 
IIRC Jan has seen similar issue too.
Comment 8 Jan Stodola 2018-01-30 16:29:33 UTC 
A problem with resolv.conf in the past was reported as bug 1327169, which turned out to be a consequence of bug 1327204 -  Two network connections reported by nmcli during installation on s390x.
/etc/resolv.conf existed in that case, but the nameserver was not set in the file.
Comment 9 Radek Vykydal 2018-01-31 09:53:27 UTC 
(In reply to Radek Vykydal from comment #2)
> May be related to bug #1537977.

It really seems to be the same issue as bug #1537977.
To confirm, you can check with updates image enabling the fedora-import-state service:
https://rvykydal.fedorapeople.org/updates.fedora-import-state.img
Comment 10 Dan Horák 2018-01-31 10:10:34 UTC 
Yes, with the provided updates image the nameserver is set in /etc/resolv.conf and installation source is set to a repo.
Comment 11 Radek Vykydal 2018-02-05 07:36:49 UTC 

*** This bug has been marked as a duplicate of bug 1537977 ***
Comment 12 Radek Vykydal 2018-02-05 07:38:03 UTC 
Should be fixed in latest rawhide Fedora-Rawhide-20180204.n.0.
Comment 13 Dan Horák 2018-02-22 10:27:39 UTC 
Verified with the branched Fedora-28-20180221.n.0 compose, thanks.
Note You need to log in before you can comment on or make changes to this bug.