Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
With Network Manager disabled, PEERDNS setting "no" must prevent resolv.conf being overwritten for any manual editing.
Version-Release number of selected component (if applicable):
RHEL7.0 Beta
How reproducible:
Steps to Reproduce:
1.Disable network manager #systemctl disable NetworkManager
2.Setup networking with static IP on /etc/sysconfig/network-scripts/ifcfg-eth0
Add line "PEERDNS=no" in the end.
3.update /etc/resolv.conf with addition nameserver etc
4.systemctl restart network
5.check if the resolv.conf was overwritten
Actual results:
/etc/resolv must be preserved after reboot/network restart
Expected results:
Manual additions to /etc/resolv gets overwritten/removed
Additional info:
As the reporter says in the description he disables NetworkManager, then this can't be a NetworkManager problem. But rather it is dealt by legacy initscripts.
However, I doubt there is a problem and the report should be probably closed.
PEERDNS is described in /usr/share/doc/initscripts/sysconfig.txt. And it is also mentioned in man nm-settings-ifcfg-rh, stating that there is a slight difference in behaviour when using NetworkManager.
For not touching resolv.conf during NetworkManager operation there is a configuration option dns=none (man NetworkManager.conf).
There are also useful links in comment #3 and comment #4.
I actually seem to be seeing this problem on F23 (but was not on F21). With F23 and this /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE="eth0"
HWADDR="XX:XX:XX:XX:XX:XX"
BOOTPROTO="dhcp"
ONBOOT="yes"
PEERDNS="no"
IPV6INIT=no
IPV6_AUTOCONF=no
DHCPV6=no
dhclient-script overwrites /etc/resolv.conf whenever the interface comes up, which PEERDNS="no" should prevent. With NetworkManager.service it seems to work correctly (resolv.conf is not overwritten).
> dhclient-script overwrites /etc/resolv.conf whenever the interface comes up,
> which PEERDNS="no" should prevent. With NetworkManager.service it seems to
> work correctly (resolv.conf is not overwritten).
That looks like a completely different issue, original report is about static ip addresses. Please file separate bug for dhcp component.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2456.html
Comment 20Red Hat Bugzilla
2023-09-14 02:07:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days