Bug 1583677 - Please backport IFDOWN_ON_SHUTDOWN from upstream
Summary: Please backport IFDOWN_ON_SHUTDOWN from upstream
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.6
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: David Kaspar [Dee'Kej]
QA Contact: Daniel Rusek
Ioanna Gkioka
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-29 13:15 UTC by Lukáš Nykrýn
Modified: 2018-10-30 10:17 UTC (History)
5 users (show)

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.
Clone Of:
Last Closed: 2018-10-30 10:15:57 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3131 0 None None None 2018-10-30 10:17:17 UTC

Description Lukáš Nykrýn 2018-05-29 13:15:01 UTC
I think we should backport https://github.com/fedora-sysv/initscripts/commit/2eaa9d1e7b682ce895d56966d9178dcfa0c822b1

In systemd, we have quite a lot of bugs with races where the network was shut down before a network disk was unmounted. This option brings a nice and simple workaround for those issues.

By default, this should be set to IFDOWN_ON_SHUTDOWN=true.

Comment 1 David Kaspar [Dee'Kej] 2018-05-29 13:17:06 UTC
Pull-request submitted:

(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.

Comment 13 errata-xmlrpc 2018-10-30 10:15:57 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.