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.
Bug 1583677 - Please backport IFDOWN_ON_SHUTDOWN from upstream
Summary: Please backport IFDOWN_ON_SHUTDOWN from upstream
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.6
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: David Kaspar // Dee'Kej
QA Contact: Daniel Rusek
Ioanna Gkioka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-29 13:15 UTC by Lukáš Nykrýn
Modified: 2021-12-10 16:15 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:
Environment:
Last Closed: 2018-10-30 10:15:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
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:
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.
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.

https://access.redhat.com/errata/RHBA-2018:3131
Note You need to log in before you can comment on or make changes to this bug.