Bug 1278521
| Summary: | Netconsole cannot resolve the syslog server address if it is only included in the /etc/hosts file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Raul Mahiques <rmahique> | ||||
| Component: | initscripts | Assignee: | David Kaspar // Dee'Kej <deekej> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Leos Pol <lpol> | ||||
| Severity: | medium | Docs Contact: | Filip Hanzelka <fhanzelk> | ||||
| Priority: | medium | ||||||
| Version: | 7.3 | CC: | deekej, jscotka, lnykryn, qe-baseos-daemons | ||||
| Target Milestone: | rc | Keywords: | Patch, Reproducer | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | initscripts-9.49.38-1.el7 | Doc Type: | Release Note | ||||
| Doc Text: |
The *netconsole* utility now launches correctly
Previously, if `nameserver` address lines were not present in the `/etc/resolv.conf` file, launching *netconsole* sometimes resulted in an error and *netconsole* did not start. The _initscripts_ package has been updated, and *netconsole* now starts correctly in this situation.
|
Story Points: | --- | ||||
| Clone Of: | 1278519 | Environment: | |||||
| Last Closed: | 2017-08-01 07:29:01 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: | 1278519, 1392766 | ||||||
| Bug Blocks: | 1298243, 1393867 | ||||||
| Attachments: |
|
||||||
|
Description
Raul Mahiques
2015-11-05 17:01:12 UTC
In the patch provided, please change the following: -if ( grep -i 'IPV6INIT=yes' /etc/sysconfig/network &>/dev/null ) +if [ "$(</proc/sys/net/ipv6/conf/all/disable_ipv6)" == '0' ] *** Bug 1398675 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-2017:2286 |