Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

On 03/06/2013 01:20 PM, Dan Kenigsberg wrote: >On Tue, Mar 05, 2013 at 10:08:48AM -0800, Rob Zwissler wrote: >>On Mon, Mar 4, 2013 at 11:46 PM, Dan Kenigsberg <danken(a)redhat.com&gt; wrote: >>>Rob, >>> >>>It seems that a bug in vdsm code is hiding the real issue. >>>Could you do a >>> >>> sed -i s/ParseError/ElementTree.ParseError /usr/share/vdsm/gluster/cli.py >>> >>>restart vdsmd, and retry? >>> >>>Bala, would you send a patch fixing the ParseError issue (and adding a >>>unit test that would have caught it on time)? > >>Traceback (most recent call last): >> File "/usr/share/vdsm/BindingXMLRPC.py", line 918, in wrapper >> res = f(*args, **kwargs) >> File "/usr/share/vdsm/gluster/api.py", line 32, in wrapper >> rv = func(*args, **kwargs) >> File "/usr/share/vdsm/gluster/api.py", line 56, in volumesList >> return {'volumes': self.svdsmProxy.glusterVolumeInfo(volumeName)} >> File "/usr/share/vdsm/supervdsm.py", line 81, in __call__ >> return callMethod() >> File "/usr/share/vdsm/supervdsm.py", line 72, in <lambda> >> **kwargs) >> File "<string>", line 2, in glusterVolumeInfo >> File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, >>in _callmethod >> raise convert_to_error(kind, result) >>AttributeError: class ElementTree has no attribute 'ParseError' > >My guess has led us nowhere, since etree.ParseError is simply missing >from python 2.6. It is to be seen only in python 2.7! > >That's sad, but something *else* is problematic, since we got to this >error-handling code. > >Could you make another try and temporarily replace ParseError with >Exception? > > sed -i s/etree.ParseError/Exception/ /usr/share/vdsm/gluster/cli.py > >(this sed is relative to the original code). > More specific sed is sed -i s/etree.ParseError/SyntaxError/ /usr/share/vdsm/gluster/cli.py