Bug 1364895
| Summary: | Updating /etc/resolv.conf failed sometimes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Akhil John <ajohn> |
| Component: | initscripts | Assignee: | David Kaferad // Dee'Kej <deekej> |
| Status: | CLOSED ERRATA | QA Contact: | Daniel Rusek <drusek> |
| Severity: | medium | Docs Contact: | Filip Hanzelka <fhanzelk> |
| Priority: | medium | ||
| Version: | 7.1 | CC: | antaylor, bdoran, carsten.grohmann, deekej, drusek, jscotka |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | initscripts-9.49.40-2.el7 | Doc Type: | Release Note |
| Doc Text: |
Network scripts now correctly update `/etc/resolv.conf`
Network scripts have been enhanced to update the `/etc/resolv.conf` file correctly. Notably:
* The scripts now update the `nameserver` and `search` entries in the `/etc/resolv.conf` file after the "DNS*" and "DOMAIN" options, respectively, have been updated in the `ifcfg-*` files in the `/etc/sysconfig/network-scripts/` directory
* The scripts now also update the order of `nameserver` entries after it has been updated in the `ifcfg-*` files in `/etc/sysconfig/network-scripts/`
* Support for the "DNS3" option has been added
* The scripts now correctly process duplicate and randomly omitted "DNS*" options
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 18:24:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1203710, 1298243, 1357658, 1380361, 1393867, 1400961, 1420851, 1465901, 1466365 | ||
|
Description
Akhil John
2016-08-08 06:50:43 UTC
Can we make this bug public ? customer is requesting for public access . (In reply to Akhil John from comment #2) > Can we make this bug public ? customer is requesting for public access . I am fine with that. > RHEL7 server without the NetworkManager packages > # cat /etc/resolv.conf > # Generated by NetworkManager Are you really sure that NetworkManager is not installed on that system? Anyway in your reproducer could you before the reboot add "set -x" to the end of /etc/init.d/functions so it looks like this: ---------------------------------------- [0 root@qeos-52 test]# tail /etc/init.d/functions "x$1" = xtry-restart -o \ "x$1" = xforce-reload -o \ "x$1" = xcondrestart ] ; then systemctl_redirect $0 $1 exit $? fi fi set -x ---------------------------------------- And then reboot the machine and attach the output of "journalctl -b" and "journalctl -b -u network.service" Looks like I have already fixed that: https://bugzilla.redhat.com/show_bug.cgi?id=1316019 Should be in 7.3. *** This bug has been marked as a duplicate of bug 1316019 *** Just for reference patch for rhel7 branch of initscripts: https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel7-branch&id=21ee08c718692c6a4ff32204767638f0c3aafa65 I wouldn't agree with closing this bug, because swapping the entries DNS1 and DNS2 in ifcfg-eth0 also does not trigger an update of /etc/resolv.conf. (In reply to Carsten Grohmann from comment #8) > I wouldn't agree with closing this bug, because swapping the entries DNS1 > and DNS2 in ifcfg-eth0 also does not trigger an update of /etc/resolv.conf. Ok, I will look into that part. Unfortunately it is quite late in 7.3 development and this is not a critical issue, so I don't think it will make it there. Also I must admit I was wrong in the case of DNS3. I have read the specification for resolving in glib and for rhel7 we have MAXNS set to 3. So that should be also supported in initscripts. I will look into that as well. Pull-request submitted into upstream: https://github.com/fedora-sysv/initscripts/pull/131 *** Bug 1548871 has been marked as a duplicate of this bug. *** 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://access.redhat.com/errata/RHBA-2018:0983 |