Bug 1583677
Summary: | Please backport IFDOWN_ON_SHUTDOWN from upstream | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Lukáš Nykrýn <lnykryn> |
Component: | initscripts | Assignee: | David Kaspar // Dee'Kej <deekej> |
Status: | CLOSED ERRATA | QA Contact: | Daniel Rusek <drusek> |
Severity: | high | Docs Contact: | Ioanna Gkioka <igkioka> |
Priority: | high | ||
Version: | 7.6 | CC: | deekej, drusek, igkioka, initscripts-maint-list, lnykryn |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | initscripts-9.49.43-1.el7 | Doc Type: | Enhancement |
Doc Text: |
A new `network-scripts` option: "IFDOWN_ON_SHUTDOWN"
This update adds the "IFDOWN_ON_SHUTDOWN" option for `network-scripts`. Setting this option to `yes`, `true`, or leaving it empty has no effect. If you set this option to `no`, or `false`, it causes the `ifdown` calls to not be issued when stopping or restarting the `network` service.
This can be useful in situations where NFS (or other network file system) mounts are in a stale state, because the network was shut down before the mount was cleanly unmounted.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 10:15:57 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: |
Description
Lukáš Nykrýn
2018-05-29 13:15:01 UTC
Pull-request submitted: https://github.com/fedora-sysv/initscripts/pull/203 (In reply to Lukáš Nykrýn from comment #0) > By default, this should be set to IFDOWN_ON_SHUTDOWN=true. Just to clarify, the current logic there assumes to use 'ifdown' on shutdown also when the IFDOWN_ON_SHUTDOWN option is empty. 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:3131 |