Red Hat Bugzilla – Bug 149860
Interface up because of "onboot=no"
Last modified: 2007-11-30 17:07:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7)
Description of problem:
we has rebooted the whole s390 LPAR on saturday, for that Linux (I
talking about) it should be the same as an "init 6".
After this server came up, he has the interface eth0:0 up, because of
that "onboot=no" was in /etc/sysconfig/network-scripts/ifcfg-eht0:0.
The matter is, that this interface only should be used when another
server wends down (manual failover). This causes a duplicate
IP-Address and there for a lot of trouble with false public ssh - keys
and so on.
At first I should think nobody was able to bring this interface up by
hand, because at the bootup I was alone and I never touched this
system directly. My application admin says that the trouble starts
directly after the boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. service network restart
Actual Results: eth0:0 is up and has an IP still exists
Expected Results: eth0:0 should be waiting for activation
/etc/sysconfig/networking/profiles/default is empty
Reproduced here, I've got virtual interface eth0:2, ifcfg-eth0:2 contains
ifdown eth0:2 stops the interface, but after `service network restart` the
interface is up again. This looks to me like a wrong parsing of the
configuration file, assigning to initscripts.
For aliases, ONPARENT=(yes|no) is used.