Hi Dan,
Thank you for the quick fix and reply!
The output of `brctl show` as follows:
bridge name bridge id STP enabled interfaces ovirtmgmt 8000.0025907c2c7a no eth0 eth2
It goes away after doing 'brctl delif ovirtmgmt eth0' manually. I will let you know if we could reproduce this issue again.
Thanks and Regards, Tim
----- Original Message -----
From: "Dan Kenigsberg" danken@redhat.com To: "Timothy Asir Jeyasingh" tjeyasin@redhat.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, June 19, 2013 4:03:20 PM Subject: Re: [vdsm] Need help on fixing VDSM node non-operational error
On Wed, Jun 19, 2013 at 05:51:52AM -0400, Timothy Asir Jeyasingh wrote:
Hi All,
Currently I am facing some issues while adding a node to an engine. Host comes up initially. Then goes to Non-operational state. On trying to activate the host, it again comes up. Then goes to Non-operational state again and so on.
The following message is seen in the engine Events log multiple times - Bridged network ovirtmgmt is attached to multiple interfaces: eth2,eth0 on Host ...
The following is seen in the engine logs - 2013-06-06 20:52:23,003 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-16) Host '...' moved to Non-Operational state because interface/s 'eth0, ' are down which needed by network/s 'ovirtmgmt, ' in the current cluster
Additional info: The host is a physical machine. The contents of the file /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt -
# cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt DEVICE=ovirtmgmt TYPE=Bridge ONBOOT=yes DELAY=0 BOOTPROTO=dhcp NM_CONTROLLED=no
The contents of /etc/sysconfig/network-scripts/ifcfg-eth2
# cat /etc/sysconfig/network-scripts/ifcfg-eth2 DEVICE="eth2" BRIDGE="ovirtmgmt" BOOTPROTO="dhcp" HWADDR="00:25:90:93:62:02" IPV6INIT="yes" IPV6_AUTOCONF="yes" NM_CONTROLLED="yes" ONBOOT="yes" TYPE="Ethernet"
The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 -
# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE="eth0" HWADDR="00:25:90:7C:2C:7A" NM_CONTROLLED="yes" ONBOOT="yes"
Can someone give some suggestion for this issue!
I've had a couple of questions on https://bugzilla.redhat.com/show_bug.cgi?id=971477#c7
What does `brctl show` have on your faulty host? (just to rule out that vdsm is lying about the ovirtmgmt being connected to two nics)
{'ovirtmgmt': {'addr': '10.70.36.44', 'cfg': {'DELAY': '0', 'NM_CONTROLLED': 'no', 'BOOTPROTO': 'dhcp', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Bridge', 'ONBOOT': 'yes'}, 'mtu': '1500', 'netmask': '255.255.254.0', 'stp': 'off', 'ports': ['eth0', 'eth2']}}
Does it reproduce on any other system? Does it go away once you manually
brctl delif ovirtmgmt eth0