Networks discovering problem

Latest response

I have installed new RHEV host (RHEL-based) and have added all cluster logical networks to host without saving and rebooted host after. After reboot I cannot add network ("Unexpected exception" is first message and "Bridge already exists" is second).

 

2012-02-01 18:22:04,644 INFO  [org.ovirt.engine.core.bll.AttachNetworkToVdsInterfaceCommand] (http-0.0.0.0-8443-2) Running command: AttachNetworkToVdsInterfaceCommand internal: false. Entities affected :  ID: c6eae3a4-4cd7-11e1-8932-0011259d9202 Type: VDS
2012-02-01 18:22:04,646 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.AddNetworkVDSCommand] (http-0.0.0.0-8443-2) START, AddNetworkVDSCommand(vdsId = c6eae3a4-4cd7-11e1-8932-0011259d9202, networkName=er50, oldNetworkName=null, hostAddr=null, checkConnectivity=false, connectionTimeout=0, vlanId=649, bondName=null, nics=[eth1], inetAddr=null, networkMask=null, gateway=, stp=false, bondingOptions=null, bootProtocol=None), log id: 64e90a5
2012-02-01 18:22:05,065 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-2) Failed in AddNetworkVDS method
2012-02-01 18:22:05,066 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-2) Error code unexpected and error message VDSGenericException: VDSErrorException: Failed to AddNetworkVDS, error = Unexpected exception
2012-02-01 18:22:05,066 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-2) Command org.ovirt.engine.core.vdsbroker.vdsbroker.AddNetworkVDSCommand return value
 Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusOnlyReturnForXmlRpc
mStatus                       Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc
mCode                         16
mMessage                      Unexpected exception


2012-02-01 18:22:05,066 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-2) Vds: 3650M2-top
2012-02-01 18:22:05,066 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (http-0.0.0.0-8443-2) Command AddNetworkVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to AddNetworkVDS, error = Unexpected exception

Update button doesn't work properly because bridges are exist and up but manager know nothing about it.

PZ
Log in to join the conversation

Responses

Sadique Puthen's picture Red Hat Guru 4679 points
2 February 2012 10:23 AM

I just test this in our internal lab and couldn't reproduce it. After rebooting the RHEL hypervisor after adding an interace to a logical network and without doing "Save network configuration", I was able to re-add it once the host was up.

 

How did you reboot the host? By running "reboot"? By using power management direcly? By usine power management from rhevm?

 

If you go to /etc/sysconfig/network-scripts, do you see ifcfg-xxxx for the new logical network?

 

If you run "brctl show" on the host, do you see a bridge with name of the new logical network?

PZ Active Contributor 240 points
3 February 2012 1:06 PM

>> How did you reboot the host? By running "reboot"? By using power management direcly? By usine power management from rhevm?

 

Rebooted by "reboot" command via ssh.

 

>> If you go to /etc/sysconfig/network-scripts, do you see ifcfg-xxxx for the new logical network?

>> If you run "brctl show" on the host, do you see a bridge with name of the new logical network?

 

 

Yes, configs exist, bridges exist too. I have deleted both bridges and configs and rebooted again, the same exception appeared,

 I'll try to reproduce this situation on fresh host installation and post progress here,

Sadique Puthen's picture Red Hat Guru 4679 points
3 February 2012 1:15 PM

If you haven't removed "BRIDGE=name" from ifcfg-ethx interface used to create the bridge, then the bridge will get again created automatically while trying to bring up ethx after reboot.

Did you remove "BRIDGE=name" from the interface config files?