Dracut's init script creates an rwtab entry for /etc/sysconfig/network-scripts and copies over an ifcfg-eth0 script. This ifcfg-eth0 script contains a line setting ONBOOT=yes. However, with a network-booted system with an NFS root, the eth0 interface is initialized by Dracut, and there is no need for the system to initialize eth0 after pivoting. In fact, the system completely hangs when trying to do so. Reinitializing eth0 requires dropping eth0 (removing access to the NFS root) and then bringing eth0 back up, which hangs because tools like dhclient are on the NFS root. What does the ifcfg-eth0 script accomplish? If it really needs to be there, would it be possible to set ONBOOT=no so that the system doesn't hang? If not, would it be possible to have a boot option to override this behavior?
(In reply to comment #0) > Dracut's init script creates an rwtab entry for /etc/sysconfig/network-scripts > and copies over an ifcfg-eth0 script. This ifcfg-eth0 script contains a line > setting ONBOOT=yes. However, with a network-booted system with an NFS root, > the eth0 interface is initialized by Dracut, and there is no need for the > system to initialize eth0 after pivoting. In fact, the system completely hangs > when trying to do so. Reinitializing eth0 requires dropping eth0 (removing > access to the NFS root) and then bringing eth0 back up, which hangs because > tools like dhclient are on the NFS root. > > What does the ifcfg-eth0 script accomplish? If it really needs to be there, > would it be possible to set ONBOOT=no so that the system doesn't hang? If not, > would it be possible to have a boot option to override this behavior? dracut only copies to /dev/.initramfs/ . The rest is up to NetworkManager.
Thanks for responding so quickly. As you pointed out, the /init script copies everything to /dev/.initramfs. However, the files are definitely getting copied over; the files in /etc/sysconfig/network-scripts are definitely different from the ones on the NFS root and: % grep network-scripts /proc/mounts none /etc/sysconfig/network-scripts tmpfs rw,relatime 0 0 % grep -R network-scripts /etc/rwtab* % After looking into this a bit more, I have found that the system's rc.sysinit sets up mounts from /dev/.initramfs/rwtab and copies everything from /dev/.initramfs/state: # Use any state passed by initramfs [ -d /dev/.initramfs/state ] && cp -a /dev/.initramfs/state/* $RW_MOUNT So, anyway, the network-scripts files are definitely getting copied over. Would it make sense for dracut to create the files with ONBOOT=no? If not, /etc/init.d/network would definitely need to be modified to be able to ignore the ifcfg-eth0 script since the eth0 interface is already active.
I have no idea why this got assigned to NetworkManager. I mentioned in comment #2 that I'm using /etc/init.d/network, so I'm not sure what NetworkManager has to do with this, unless NetworkManager is the reason for the ONBOOT=yes setting. Thanks.
This is supposed to work - dracut also supplies the dhclient leases file which should cause dhclient to just take over the lease. If it's static, that is also supposed to be a non-destructive operation.
In both Fedora 11 and Fedora 12 (I'm not sure about previous versions), any time /etc/init.d/network tries to start the network interfaces, the system hangs forever. I've used various workarounds over the last year, including setting ONBOOT=no and replacing /etc/init.d/network with a script that just touches /var/lock/subsys/network. I've had the problem both with and without bridging enabled.
I forgot to mention that when bridging is enabled, it gives an extra error message about how it couldn't bind eth0 to br0 because it was already bound to a bridge (since eth0 was already bound to br0).
Dracut doesn't copy the state unless "rdcopystate" is given as am argument. The comment in the dracut init indicates that this is for debugging, which is misleading at best. This argument is pretty much essential when netbooting with dhcp.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping