Red Hat Bugzilla – Bug 253146
initscripts gets rid of ifcfg-eth0 script
Last modified: 2014-03-16 23:08:03 EDT
Upgrading to initscripts-8.55-1 caused /etc/sysconfig/network-scripts/ifcfg-eth0 to be renamed to ifcfg-eth0.bak and not replaced, thus rendering my network out of order. It seems there's a bug in the recent changes to make updates to the ifcfg-eth* files. Might it have something to do with the fact that I also have a ifcfg-eth0:1? I'll attach them in case it'll help.
Created attachment 161718 [details] ifcfg-eth0
Created attachment 161719 [details] ifcfg-eth0:1
It wasn't initscripts; kudzu renamed it to .bak because the device disappeared when you rebooted. Did it exist as a different name after booting, or did driver initialization fail?
I don't run kudzu on boot; I have it disabled. I suppose it's possible that I ran it by hand and it did what you said, but I just ran it by hand again, and my ifcfg-eth0 script remained unmolested after I did so. I didn't see any evidence that eth0 was missing or its driver failed when this problem occurred, but I certainly could have missed it.
kudzu's the only thing that will rename ifcfg-eth0 to ifcfg-eth0.bak, though (with the possible exception of a manual system-config-network run.) initscripts doesn't touch ifcfg-XXXX outside of lo.
Having the same problems with initscripts-8.60-1 (F8 update from March 27, 2008).
I have to modify: same problem with kudzu-1.2.79.2-1 (F8 update from March 27, 2008)
Same problem but is not kudzu: > chkconfig --list kudzu kudzu 0:off 1:off 2:off 3:off 4:off 5:off 6:off * Machine was OK * I upgraded to the latest kernel * Machine was still OK (i.e., /etc/sysconfig/network-scripts/ifcfg-eth0 was still configured with a static address) * Rebooted * Machine was configured with DHCP (which is bad since it was not reachable)
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I see this on RHEL5 from time to time when I reboot a cluster node. I haven't been able to figure out what is renaming ifcfg-eth[01] or why.
Created attachment 317824 [details] First hwconf from marathon-01 I'm attaching two version of /etc/sysconfig/hwconf from a node that has hit this issue. There are differences in subDeviceId.
Created attachment 317825 [details] Second hwconf from marathon-01
That would be why it changes in your case - all of vendor/device/subvendor/subdevice are taken into account.
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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
Given comments 12/13, closing.
I get the exact same behaviour on RHEL5 when I: 1/ back up the machine configuration (/etc/sysconfig/network, /etc/sysconfig/network-scripts*, /etc/ssh/) 2/ restore a complete O/S from a different machine 3/ restore the aforementioned data 4/ reboot The physical machine stays exactly the same, but Kudzu honestly believes it has to disable all my interfaces. (very annoying on a cluster node) Is there any way to avoid this behavior?
There are patches for this in 5.6 that may help.