Bug 783470

Summary: Network changes are reset when network.service is restarted
Product: [Fedora] Fedora Reporter: Simon Andrews <simon.andrews>
Component: system-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: harald, jpopelka, matt.castelein
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 14:28:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Simon Andrews 2012-01-20 14:48:14 UTC
Description of problem:

When running with just network.service (not NetworkManager) DNS changes made with system-config-network-tui are lost when network-service is restarted.

Version-Release number of selected component (if applicable):
system-config-network-tui-1.6.3-1.fc16.noarch
systemd-37-3.fc16.x86_64
initscripts-9.34-2.fc16.x86_64

How reproducible:
Always (on the affected machine at least)

Steps to Reproduce:
1. Run system-config-network-tui
2. Change DNS servers and search path
3. Check /etc/resolvl.conf - looks OK
4. Run systemctl restart network.service
5. Check /etc/resolv.conf
  
Actual results:

After running system-config-network-tui resolv.conf reads:
search example.com
nameserver 192.168.144.1
nameserver 192.168.144.2
nameserver 192.168.144.3


After running systemctl restart network.service resolv.conf reads:
nameserver 192.168.144.1
nameserver 192.168.144.2

..so the third DNS server and the search path are lost.

/var/log/messages says:

NET[24021]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf

Expected results:

Settings from system-config-network are preserved after a service restart.

Additional info:

For the record NetworkManger is definitely not running, and the interface being restarted has the following ifcfg-eth0 file:

$ more ifcfg-eth0
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.151.255
HWADDR=00:4f:4f:2e:2e:52
IPADDR=192.168.144.80
NETMASK=255.255.248.0
NETWORK=192.168.144.0
ONBOOT=yes
DNS1=192.168.144.1
DNS2=192.168.144.2
SEARCH=example.com
NM_CONTROLLED=no
GATEWAY=192.168.144.200
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
PREFIX=21

Comment 1 Jiri Popelka 2012-01-20 15:41:03 UTC
I think the problem is that system-config-network-tui enables to specify 3 DNS servers when initscripts allow to specify only 2.

From /usr/share/doc/initscripts-9.34/sysconfig.txt:
DNS{1,2}=<ip address>
      provide DNS addresses that are dropped into the resolv.conf
      file if PEERDNS is not set to "no".

Also I don't see any any 'SEARCH=' option in sysconfig.txt.
Looking at ifup-post it seems that correct option is 'DOMAIN='

Can you try to manually change
SEARCH=example.com
to
DOMAIN=example.com
in the ifcfg-eth0 to see if I'm right ?

Comment 2 Simon Andrews 2012-01-20 16:14:01 UTC
Will try that suggestion. I also found that removing the DNS settings from the ifcfg-et0 file, or adding PEERDNS=no as an extra options should fix this.

Comment 3 Fedora End Of Life 2013-01-16 13:37:28 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 14:28:43 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.