Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When using a network block device, in my case iSCSI, the network.service will disable the network interface during reboot or shutdown. This causes the root file system to go offline during shutdown and the system hangs.
My test setup was getting two network configurations files with different names (eth0 and ibft0), one created by anaconda and one by dracut at each boot. This was causing network.service to enter a failed state on boot, and therefor was never being stopped at shutdown. If I remove the ifcfg-eth0 file and fix the service start, then I start having the problems at shutdown.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Install to a network block device
2. Make sure that network.service started successfully
3. Try and reboot
Actual results:
system hangs at stopping network.service, kernel messages indicate that the iSCSI session has suffered a connection error due to network interface going offline
Expected results:
clean reboot
Additional info:
/etc/init.d/network checks for a _netdev mount option flag on the root filesystem in /etc/mtab, but because /etc/mtab is now a symlink to /proc/self/mounts those options which the kernel is unaware of are no longer saved from /etc/fstab to /etc/mtab. This check always fails and all network interfaces are disabled during shutdown.
Forcing an exit at this point in the service script, as if the _netdev option has been found, seems to fix this for me.
dracut is putting a NETBOOT=yes value in ifcfg-ibft0, but neither the legacy network scripts nor NetworkManager appear to be aware of this at all.
I think that disabling network.service should help in this case. Network manager does not terminate network during shutdown.
Comment 3RHEL Program Management
2014-04-02 05:47:36 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Resolving the NEEDINFO:
Per comment #5:
> Could you please let us know which RHEL 7 build this fix will make it into ?
and comment #6> Patch is in 9.49.16-1.
The initscripts version containing the fix is 9.49.16-1.
RHEL7.0 GA contained initscripts-9.49.17-1.