[Users] Setup Networks: Unexpected exception

Dan Kenigsberg danken at redhat.com
Tue Jan 28 09:47:11 UTC 2014


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:
> > > > <err> = '0+1 records in\n0+1 records out\n512 bytes (512 B) copied,
> > > > 0.000273105 s, 1.9 MB/s\n'; <rc> = 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 <lambda>
> > > >     **kwargs)
> > > >   File "<string>", 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.



More information about the Users mailing list