Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Dan Kenigsberg
On Tue, Jan 28, 2014 at 11:07:46AM +0100, Frank Wall wrote:
> On Tue, Jan 28, 2014 at 09:47:11AM +, Dan Kenigsberg wrote:
> > Frank, can you tell how did it reach your ovirt-3.4 installation? Did
> > you pull a nightly build of Vdsm ?
> 
> Indeed, I'm currently testing vdsm nightly along with oVirt-Engine 3.4 Beta:
> 
> ovirt-engine:
> ovirt-engine-3.4.0-0.5.beta1.el6.noarch
> 
> ovirt node:
> vdsm-4.14.1-17.gitcf59a55.el6.x86_64
> ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch

Thank you for that!
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Frank Wall
On Tue, Jan 28, 2014 at 09:47:11AM +, Dan Kenigsberg wrote:
> Frank, can you tell how did it reach your ovirt-3.4 installation? Did
> you pull a nightly build of Vdsm ?

Indeed, I'm currently testing vdsm nightly along with oVirt-Engine 3.4 Beta:

ovirt-engine:
ovirt-engine-3.4.0-0.5.beta1.el6.noarch

ovirt node:
vdsm-4.14.1-17.gitcf59a55.el6.x86_64
ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch


Regards
- Frank
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Dan Kenigsberg
On Tue, Jan 28, 2014 at 04:15:56AM -0500, Antoni Segura Puimedon wrote:
> 
> > > 
> > > Looks related to the recently merged:
> > > http://gerrit.ovirt.org/#/c/23366/
> > 
> > Indeed! My bad in +1 it. The ifcfg.py implementation refers
> > to self thinking it is the configurator but from the configwriter,
> > which does not have access to the method.
> 
> Fix posted: http://gerrit.ovirt.org/#/c/23792/

Frank, thanks for reporting this; Toni, thanks for the quick fix.
It has been a very misearble verification on my part. I most probably
verified the last revision of my patch only with the non-default
iproute2 configurator.

> > > > 23:41:09,871::fileSD::225::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
> > > >  = '0+1 records in\n0+1 records out\n512 bytes (512 B) copied,
> > > > 0.000273105 s, 1.9 MB/s\n';  = 0
> > > > Thread-119::ERROR::2014-01-27
> > > > 23:41:10,119::BindingXMLRPC::989::vds::(wrapper) unexpected error
> > > > Traceback (most recent call last):
> > > >   File "/usr/share/vdsm/BindingXMLRPC.py", line 973, in wrapper
> > > > res = f(*args, **kwargs)
> > > >   File "/usr/share/vdsm/BindingXMLRPC.py", line 402, in setupNetworks
> > > > return api.setupNetworks(networks, bondings, options)
> > > >   File "/usr/share/vdsm/API.py", line 1294, in setupNetworks
> > > > supervdsm.getProxy().setupNetworks(networks, bondings, options)
> > > >   File "/usr/share/vdsm/supervdsm.py", line 50, in __call__
> > > > return callMethod()
> > > >   File "/usr/share/vdsm/supervdsm.py", line 48, in 
> > > > **kwargs)
> > > >   File "", line 2, in setupNetworks
> > > >   File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in
> > > >   _callmethod
> > > > raise convert_to_error(kind, result)
> > > > AttributeError: 'ConfigWriter' object has no attribute 'getEthtoolOpts'
> > > > 
> > > 
> > > Seems the failure on vdsm side. Adding Toni and Assaf.

I do not understand one thing: the offensive code with getEthtoolOpts
was merged only to the "master" branch.

Frank, can you tell how did it reach your ovirt-3.4 installation? Did
you pull a nightly build of Vdsm ?

Regards,
Dan.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Antoni Segura Puimedon


- Original Message -
> From: "Antoni Segura Puimedon" 
> To: "Assaf Muller" 
> Cc: users@ovirt.org
> Sent: Tuesday, January 28, 2014 10:02:39 AM
> Subject: Re: [Users] Setup Networks: Unexpected exception
> 
> 
> 
> - Original Message -
> > From: "Assaf Muller" 
> > To: "Dan Kenigsberg" 
> > Cc: "Frank Wall" , "Antoni Segura Puimedon"
> > , users@ovirt.org, "Moti Asayag"
> > 
> > Sent: Tuesday, January 28, 2014 9:58:12 AM
> > Subject: Re: [Users] Setup Networks: Unexpected exception
> > 
> > Looks related to the recently merged:
> > http://gerrit.ovirt.org/#/c/23366/
> 
> Indeed! My bad in +1 it. The ifcfg.py implementation refers
> to self thinking it is the configurator but from the configwriter,
> which does not have access to the method.

Fix posted: http://gerrit.ovirt.org/#/c/23792/
> 
> > 
> > 
> > Assaf Muller, Cloud Networking Engineer
> > Red Hat
> > 
> > - Original Message -
> > From: "Moti Asayag" 
> > To: "Frank Wall" , "Antoni Segura Puimedon"
> > , "Assaf Muller" 
> > Cc: users@ovirt.org
> > Sent: Tuesday, January 28, 2014 10:41:46 AM
> > Subject: Re: [Users] Setup Networks: Unexpected exception
> > 
> > 
> > - Original Message -
> > > From: "Frank Wall" 
> > > To: users@ovirt.org
> > > Sent: Tuesday, January 28, 2014 1:31:41 AM
> > > Subject: [Users] Setup Networks: Unexpected exception
> > > 
> > > Hi,
> > > 
> > > still testing 3.4 and I'm unable to save a node's
> > > network configuration in webadmin:
> > > 
> > > Error while executing action Setup Networks: Unexpected exception
> > > 
> > > My configuration on the ovirt node:
> > > - manually added net2 bridge, attached to eth1
> > > 
> > > My configuration in ovirt-engine webadmin:
> > > - added new network net2
> > > - noticed that ovirt failed to find this network on node
> > > - tried to add net2 to node with "Setup Host Networks"
> > > 
> > > Error in engine.log [1].
> > > Error in vdsm.log [2].
> > > 
> > > I think it could be related to BZ 1054195:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1054195 ([NetworkLabels]
> > > Attaching two labeled networks to a cluster result in failure of the
> > > latter)
> > > 
> > 
> > It shouldn't be related to this bug since you haven't provided any label
> > to the network and neither configured a label on the host nic.
> > But it would be nice to use the 'network labels' feature to ease
> > network configuration on hosts.
> > 
> > > I'm not sure, because I only wanted to add *one* new network.
> > > Please note that this is a self-hosted engine setup. Just in
> > > case this makes a difference...
> > > 
> > > ovirt-engine:
> > > ovirt-engine-3.4.0-0.5.beta1.el6.noarch
> > > 
> > > ovirt node:
> > > vdsm-4.14.1-17.gitcf59a55.el6.x86_64
> > > ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch
> > > 
> > > 
> > > Thanks
> > > - Frank
> > > 
> > > [1]
> > > 2014-01-27 23:41:08,813 INFO
> > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
> > > (ajp--127.0.0.1-8702-10) [1
> > > 783e132] START, SetupNetworksVDSCommand(HostName = mgt03rn.example.com,
> > > HostId = a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, for
> > > ce=false, checkConnectivity=true, conectivityTimeout=120,
> > > networks=[net2 {id=db98fa95-e922-4060-8d39-f9ac0cb2f16f,
> > > description=Jumphost Network, comment=null, subnet=null,
> > > gateway=null, type=null, vlanId=null, stp=false,
> > > dataCenterId=0002-0002-0002-0002-0002, mtu=0, vmNetwork=true,
> > > cl
> > > uster=NetworkCluster {id={clusterId=null, networkId=null},
> > > status=OPERATIONAL, display=false, required=true, migration=false}
> > > , providedBy=null, label=null, qosId=null}],
> > > bonds=[],
> > > interfaces=[bond001 {id=c5b50ccf-5b74-4737-b7cd-980c9c8acf51,
> > > vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=bond001,
> > > macAddress=2c:44:fd:82:f5:5f, networkName=null,
> > > bondOptions=mode=802.3ad, bootProtocol=STATIC_IP,
> > > address=10.0.0.103, 

Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Antoni Segura Puimedon


- Original Message -
> From: "Assaf Muller" 
> To: "Dan Kenigsberg" 
> Cc: "Frank Wall" , "Antoni Segura Puimedon" 
> , users@ovirt.org, "Moti Asayag"
> 
> Sent: Tuesday, January 28, 2014 9:58:12 AM
> Subject: Re: [Users] Setup Networks: Unexpected exception
> 
> Looks related to the recently merged:
> http://gerrit.ovirt.org/#/c/23366/

Indeed! My bad in +1 it. The ifcfg.py implementation refers
to self thinking it is the configurator but from the configwriter,
which does not have access to the method.

> 
> 
> Assaf Muller, Cloud Networking Engineer
> Red Hat
> 
> - Original Message -
> From: "Moti Asayag" 
> To: "Frank Wall" , "Antoni Segura Puimedon"
> , "Assaf Muller" 
> Cc: users@ovirt.org
> Sent: Tuesday, January 28, 2014 10:41:46 AM
> Subject: Re: [Users] Setup Networks: Unexpected exception
> 
> 
> - Original Message -
> > From: "Frank Wall" 
> > To: users@ovirt.org
> > Sent: Tuesday, January 28, 2014 1:31:41 AM
> > Subject: [Users] Setup Networks: Unexpected exception
> > 
> > Hi,
> > 
> > still testing 3.4 and I'm unable to save a node's
> > network configuration in webadmin:
> > 
> > Error while executing action Setup Networks: Unexpected exception
> > 
> > My configuration on the ovirt node:
> > - manually added net2 bridge, attached to eth1
> > 
> > My configuration in ovirt-engine webadmin:
> > - added new network net2
> > - noticed that ovirt failed to find this network on node
> > - tried to add net2 to node with "Setup Host Networks"
> > 
> > Error in engine.log [1].
> > Error in vdsm.log [2].
> > 
> > I think it could be related to BZ 1054195:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1054195 ([NetworkLabels]
> > Attaching two labeled networks to a cluster result in failure of the
> > latter)
> > 
> 
> It shouldn't be related to this bug since you haven't provided any label
> to the network and neither configured a label on the host nic.
> But it would be nice to use the 'network labels' feature to ease
> network configuration on hosts.
> 
> > I'm not sure, because I only wanted to add *one* new network.
> > Please note that this is a self-hosted engine setup. Just in
> > case this makes a difference...
> > 
> > ovirt-engine:
> > ovirt-engine-3.4.0-0.5.beta1.el6.noarch
> > 
> > ovirt node:
> > vdsm-4.14.1-17.gitcf59a55.el6.x86_64
> > ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch
> > 
> > 
> > Thanks
> > - Frank
> > 
> > [1]
> > 2014-01-27 23:41:08,813 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
> > (ajp--127.0.0.1-8702-10) [1
> > 783e132] START, SetupNetworksVDSCommand(HostName = mgt03rn.example.com,
> > HostId = a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, for
> > ce=false, checkConnectivity=true, conectivityTimeout=120,
> > networks=[net2 {id=db98fa95-e922-4060-8d39-f9ac0cb2f16f,
> > description=Jumphost Network, comment=null, subnet=null,
> > gateway=null, type=null, vlanId=null, stp=false,
> > dataCenterId=0002-0002-0002-0002-0002, mtu=0, vmNetwork=true,
> > cl
> > uster=NetworkCluster {id={clusterId=null, networkId=null},
> > status=OPERATIONAL, display=false, required=true, migration=false}
> > , providedBy=null, label=null, qosId=null}],
> > bonds=[],
> > interfaces=[bond001 {id=c5b50ccf-5b74-4737-b7cd-980c9c8acf51,
> > vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=bond001,
> > macAddress=2c:44:fd:82:f5:5f, networkName=null,
> > bondOptions=mode=802.3ad, bootProtocol=STATIC_IP,
> > address=10.0.0.103, subnet=255.255.255.0, gateway=null, mtu=1500,
> > bridged=false, type=0, networkImplementationDetails=null},
> > eth3 {id=7aaf1ac1-944a-4fe6-9d22-7dc41c6e275c,
> > vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth3,
> > macAddress=2C:44:FD:82:F5:5F, networkName=null,
> > bondName=bond001, bootProtocol=NONE, address=, subnet=,
> > gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
> > networkImplementationDetails=null},
> > eth4 {id=0c23834d-97ae-462a-9701-e89b3dc6a83a,
> > vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth4,
> > macAddress=D8:9D:67:22:B6:4C, networkName=null,
> >

Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Assaf Muller
Looks related to the recently merged:
http://gerrit.ovirt.org/#/c/23366/


Assaf Muller, Cloud Networking Engineer 
Red Hat 

- Original Message -
From: "Moti Asayag" 
To: "Frank Wall" , "Antoni Segura Puimedon" 
, "Assaf Muller" 
Cc: users@ovirt.org
Sent: Tuesday, January 28, 2014 10:41:46 AM
Subject: Re: [Users] Setup Networks: Unexpected exception


- Original Message -
> From: "Frank Wall" 
> To: users@ovirt.org
> Sent: Tuesday, January 28, 2014 1:31:41 AM
> Subject: [Users] Setup Networks: Unexpected exception
> 
> Hi,
> 
> still testing 3.4 and I'm unable to save a node's
> network configuration in webadmin:
> 
> Error while executing action Setup Networks: Unexpected exception
> 
> My configuration on the ovirt node:
> - manually added net2 bridge, attached to eth1
> 
> My configuration in ovirt-engine webadmin:
> - added new network net2
> - noticed that ovirt failed to find this network on node
> - tried to add net2 to node with "Setup Host Networks"
> 
> Error in engine.log [1].
> Error in vdsm.log [2].
> 
> I think it could be related to BZ 1054195:
> https://bugzilla.redhat.com/show_bug.cgi?id=1054195 ([NetworkLabels]
> Attaching two labeled networks to a cluster result in failure of the latter)
> 

It shouldn't be related to this bug since you haven't provided any label
to the network and neither configured a label on the host nic.
But it would be nice to use the 'network labels' feature to ease
network configuration on hosts.

> I'm not sure, because I only wanted to add *one* new network.
> Please note that this is a self-hosted engine setup. Just in
> case this makes a difference...
> 
> ovirt-engine:
> ovirt-engine-3.4.0-0.5.beta1.el6.noarch
> 
> ovirt node:
> vdsm-4.14.1-17.gitcf59a55.el6.x86_64
> ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch
> 
> 
> Thanks
> - Frank
> 
> [1]
> 2014-01-27 23:41:08,813 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
> (ajp--127.0.0.1-8702-10) [1
> 783e132] START, SetupNetworksVDSCommand(HostName = mgt03rn.example.com,
> HostId = a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, for
> ce=false, checkConnectivity=true, conectivityTimeout=120,
> networks=[net2 {id=db98fa95-e922-4060-8d39-f9ac0cb2f16f,
> description=Jumphost Network, comment=null, subnet=null,
> gateway=null, type=null, vlanId=null, stp=false,
> dataCenterId=0002-0002-0002-0002-0002, mtu=0, vmNetwork=true, cl
> uster=NetworkCluster {id={clusterId=null, networkId=null},
> status=OPERATIONAL, display=false, required=true, migration=false}
> , providedBy=null, label=null, qosId=null}],
> bonds=[],
> interfaces=[bond001 {id=c5b50ccf-5b74-4737-b7cd-980c9c8acf51,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=bond001,
> macAddress=2c:44:fd:82:f5:5f, networkName=null,
> bondOptions=mode=802.3ad, bootProtocol=STATIC_IP,
> address=10.0.0.103, subnet=255.255.255.0, gateway=null, mtu=1500,
> bridged=false, type=0, networkImplementationDetails=null},
> eth3 {id=7aaf1ac1-944a-4fe6-9d22-7dc41c6e275c,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth3,
> macAddress=2C:44:FD:82:F5:5F, networkName=null,
> bondName=bond001, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
> networkImplementationDetails=null},
> eth4 {id=0c23834d-97ae-462a-9701-e89b3dc6a83a,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth4,
> macAddress=D8:9D:67:22:B6:4C, networkName=null,
> bondName=bond001, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
> networkImplementationDetails=null},
> eth1 {id=54cb3cf6-c4bd-4907-bf28-9020022965d5,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth1,
> macAddress=2c:44:fd:82:f5:5d, networkName=net2,
> bondName=null, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=0, bridged=true, speed=1000, type=0,
> networkImplementationDetails=null},
> eth2 {id=a53c448f-8061-460f-9c24-3081a2376de7,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth2,
> macAddress=2c:44:fd:82:f5:5e, networkName=null,
> bondName=null, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
>

Re: [Users] Setup Networks: Unexpected exception

2014-01-28 Thread Moti Asayag

- Original Message -
> From: "Frank Wall" 
> To: users@ovirt.org
> Sent: Tuesday, January 28, 2014 1:31:41 AM
> Subject: [Users] Setup Networks: Unexpected exception
> 
> Hi,
> 
> still testing 3.4 and I'm unable to save a node's
> network configuration in webadmin:
> 
> Error while executing action Setup Networks: Unexpected exception
> 
> My configuration on the ovirt node:
> - manually added net2 bridge, attached to eth1
> 
> My configuration in ovirt-engine webadmin:
> - added new network net2
> - noticed that ovirt failed to find this network on node
> - tried to add net2 to node with "Setup Host Networks"
> 
> Error in engine.log [1].
> Error in vdsm.log [2].
> 
> I think it could be related to BZ 1054195:
> https://bugzilla.redhat.com/show_bug.cgi?id=1054195 ([NetworkLabels]
> Attaching two labeled networks to a cluster result in failure of the latter)
> 

It shouldn't be related to this bug since you haven't provided any label
to the network and neither configured a label on the host nic.
But it would be nice to use the 'network labels' feature to ease
network configuration on hosts.

> I'm not sure, because I only wanted to add *one* new network.
> Please note that this is a self-hosted engine setup. Just in
> case this makes a difference...
> 
> ovirt-engine:
> ovirt-engine-3.4.0-0.5.beta1.el6.noarch
> 
> ovirt node:
> vdsm-4.14.1-17.gitcf59a55.el6.x86_64
> ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch
> 
> 
> Thanks
> - Frank
> 
> [1]
> 2014-01-27 23:41:08,813 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]
> (ajp--127.0.0.1-8702-10) [1
> 783e132] START, SetupNetworksVDSCommand(HostName = mgt03rn.example.com,
> HostId = a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, for
> ce=false, checkConnectivity=true, conectivityTimeout=120,
> networks=[net2 {id=db98fa95-e922-4060-8d39-f9ac0cb2f16f,
> description=Jumphost Network, comment=null, subnet=null,
> gateway=null, type=null, vlanId=null, stp=false,
> dataCenterId=0002-0002-0002-0002-0002, mtu=0, vmNetwork=true, cl
> uster=NetworkCluster {id={clusterId=null, networkId=null},
> status=OPERATIONAL, display=false, required=true, migration=false}
> , providedBy=null, label=null, qosId=null}],
> bonds=[],
> interfaces=[bond001 {id=c5b50ccf-5b74-4737-b7cd-980c9c8acf51,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=bond001,
> macAddress=2c:44:fd:82:f5:5f, networkName=null,
> bondOptions=mode=802.3ad, bootProtocol=STATIC_IP,
> address=10.0.0.103, subnet=255.255.255.0, gateway=null, mtu=1500,
> bridged=false, type=0, networkImplementationDetails=null},
> eth3 {id=7aaf1ac1-944a-4fe6-9d22-7dc41c6e275c,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth3,
> macAddress=2C:44:FD:82:F5:5F, networkName=null,
> bondName=bond001, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
> networkImplementationDetails=null},
> eth4 {id=0c23834d-97ae-462a-9701-e89b3dc6a83a,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth4,
> macAddress=D8:9D:67:22:B6:4C, networkName=null,
> bondName=bond001, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
> networkImplementationDetails=null},
> eth1 {id=54cb3cf6-c4bd-4907-bf28-9020022965d5,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth1,
> macAddress=2c:44:fd:82:f5:5d, networkName=net2,
> bondName=null, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=0, bridged=true, speed=1000, type=0,
> networkImplementationDetails=null},
> eth2 {id=a53c448f-8061-460f-9c24-3081a2376de7,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth2,
> macAddress=2c:44:fd:82:f5:5e, networkName=null,
> bondName=null, bootProtocol=NONE, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=1000, type=0,
> networkImplementationDetails=null},
> eth5 {id=e9f15827-bb15-41d9-8ccc-49d812cde8a6,
> vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth5,
> macAddress=d8:9d:67:22:b6:4d, networkName=null,
> bondName=null, bootProtocol=DHCP, address=, subnet=,
> gateway=null, mtu=1500, bridged=false, speed=0, type

[Users] Setup Networks: Unexpected exception

2014-01-27 Thread Frank Wall
Hi,

still testing 3.4 and I'm unable to save a node's 
network configuration in webadmin:

Error while executing action Setup Networks: Unexpected exception

My configuration on the ovirt node:
- manually added net2 bridge, attached to eth1

My configuration in ovirt-engine webadmin:
- added new network net2
- noticed that ovirt failed to find this network on node
- tried to add net2 to node with "Setup Host Networks"

Error in engine.log [1].
Error in vdsm.log [2].

I think it could be related to BZ 1054195:
https://bugzilla.redhat.com/show_bug.cgi?id=1054195 ([NetworkLabels] Attaching 
two labeled networks to a cluster result in failure of the latter)

I'm not sure, because I only wanted to add *one* new network.
Please note that this is a self-hosted engine setup. Just in
case this makes a difference...

ovirt-engine:
ovirt-engine-3.4.0-0.5.beta1.el6.noarch

ovirt node:
vdsm-4.14.1-17.gitcf59a55.el6.x86_64
ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch


Thanks
- Frank

[1]
2014-01-27 23:41:08,813 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] 
(ajp--127.0.0.1-8702-10) [1
783e132] START, SetupNetworksVDSCommand(HostName = mgt03rn.example.com, HostId 
= a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, for
ce=false, checkConnectivity=true, conectivityTimeout=120,
networks=[net2 {id=db98fa95-e922-4060-8d39-f9ac0cb2f16f, 
description=Jumphost Network, comment=null, subnet=null, 
gateway=null, type=null, vlanId=null, stp=false, 
dataCenterId=0002-0002-0002-0002-0002, mtu=0, vmNetwork=true, cl
uster=NetworkCluster {id={clusterId=null, networkId=null}, status=OPERATIONAL, 
display=false, required=true, migration=false}
, providedBy=null, label=null, qosId=null}],
bonds=[],
interfaces=[bond001 {id=c5b50ccf-5b74-4737-b7cd-980c9c8acf51, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=bond001, 
macAddress=2c:44:fd:82:f5:5f, networkName=null, bondOptions=mode=802.3ad, 
bootProtocol=STATIC_IP, address=10.0.0.103, subnet=255.255.255.0, gateway=null, 
mtu=1500, bridged=false, type=0, networkImplementationDetails=null},
eth3 {id=7aaf1ac1-944a-4fe6-9d22-7dc41c6e275c, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth3, 
macAddress=2C:44:FD:82:F5:5F, networkName=null, bondName=bond001, 
bootProtocol=NONE, address=, subnet=, gateway=null, mtu=1500, bridged=false, 
speed=1000, type=0, networkImplementationDetails=null},
eth4 {id=0c23834d-97ae-462a-9701-e89b3dc6a83a, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth4, 
macAddress=D8:9D:67:22:B6:4C, networkName=null, bondName=bond001, 
bootProtocol=NONE, address=, subnet=, gateway=null, mtu=1500, bridged=false, 
speed=1000, type=0, networkImplementationDetails=null},
eth1 {id=54cb3cf6-c4bd-4907-bf28-9020022965d5, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth1, 
macAddress=2c:44:fd:82:f5:5d, networkName=net2, bondName=null, 
bootProtocol=NONE, address=, subnet=, gateway=null, mtu=0, bridged=true, 
speed=1000, type=0, networkImplementationDetails=null},
eth2 {id=a53c448f-8061-460f-9c24-3081a2376de7, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth2, 
macAddress=2c:44:fd:82:f5:5e, networkName=null, bondName=null, 
bootProtocol=NONE, address=, subnet=, gateway=null, mtu=1500, bridged=false, 
speed=1000, type=0, networkImplementationDetails=null},
eth5 {id=e9f15827-bb15-41d9-8ccc-49d812cde8a6, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth5, 
macAddress=d8:9d:67:22:b6:4d, networkName=null, bondName=null, 
bootProtocol=DHCP, address=, subnet=, gateway=null, mtu=1500, bridged=false, 
speed=0, type=0, networkImplementationDetails=null},
eth0 {id=b4aea8bc-bdde-4e1e-a206-46ee853220c0, 
vdsId=a11f5383-b8f7-4bed-b1f3-3c7c46ecbe7a, name=eth0, 
macAddress=2c:44:fd:82:f5:5c, networkName=ovirtmgmt, bondName=null, 
bootProtocol=STATIC_IP, address=10.0.0.103, subnet=255.255.0.0, 
gateway=10.0.0.1, mtu=1500, bridged=true, speed=1000, type=2, 
networkImplementationDetails={inSync=true, managed=true}}],
removedNetworks=[],
removedBonds=[]), log id: 78e823a3
2014-01-27 23:41:08,817 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] 
(ajp--127.0.0.1-8702-10) [1783e132] FINISH, SetupNetworksVDSCommand, log id: 
78e823a3
2014-01-27 23:41:09,323 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] 
(ajp--127.0.0.1-8702-10) [1783e132] Failed in SetupNetworksVDS method
2014-01-27 23:41:09,323 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] 
(ajp--127.0.0.1-8702-10) [1783e132] 
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: 
VDSGenericException: VDSErrorException: Failed to SetupNetworksVDS, error = 
Unexpected exception, code = 16
2014-01-27 23:41:09,324 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] 
(ajp--127.0.0.1-8702-10) [1783e132] Command SetupNetworksVDSCommand(Hos