[Users] oVirt 3.2 on CentOS with Gluster 3.3

[Balamurugan Arumugam]

On 03/05/2013 01:16 PM, Dan Kenigsberg wrote:
> On Mon, Mar 04, 2013 at 04:38:50PM -0800, Rob Zwissler wrote:
>> Running CentOS 6.3 with the following VDSM packages from dre's repo:
>>
>> vdsm-xmlrpc-4.10.3-0.30.19.el6.noarch
>> vdsm-gluster-4.10.3-0.30.19.el6.noarch
>> vdsm-python-4.10.3-0.30.19.el6.x86_64
>> vdsm-4.10.3-0.30.19.el6.x86_64
>> vdsm-cli-4.10.3-0.30.19.el6.noarch
>>
>> And the following gluster packages from the gluster repo:
>>
>> glusterfs-3.3.1-1.el6.x86_64
>> glusterfs-fuse-3.3.1-1.el6.x86_64
>> glusterfs-vim-3.2.7-1.el6.x86_64
>> glusterfs-server-3.3.1-1.el6.x86_64
>>
>> I get the following errors in vdsm.log:
>>
>> Thread-1483::DEBUG::2013-03-04
>> 16:35:27,427::BindingXMLRPC::913::vds::(wrapper) client
>> [10.33.9.73]::call volumesList with () {}
>> MainProcess|Thread-1483::DEBUG::2013-03-04
>> 16:35:27,429::misc::84::Storage.Misc.excCmd::(<lambda>)
>> '/usr/sbin/gluster --mode=script volume info --xml' (cwd None)
>> MainProcess|Thread-1483::DEBUG::2013-03-04
>> 16:35:27,480::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err>
>> = ''; <rc> = 0
>> MainProcess|Thread-1483::ERROR::2013-03-04
>> 16:35:27,480::supervdsmServer::80::SuperVdsm.ServerCallback::(wrapper)
>> Error in wrapper
>> Traceback (most recent call last):
>>    File "/usr/share/vdsm/supervdsmServer.py", line 78, in wrapper
>>      return func(*args, **kwargs)
>>    File "/usr/share/vdsm/supervdsmServer.py", line 352, in wrapper
>>      return func(*args, **kwargs)
>>    File "/usr/share/vdsm/gluster/cli.py", line 45, in wrapper
>>      return func(*args, **kwargs)
>>    File "/usr/share/vdsm/gluster/cli.py", line 430, in volumeInfo
>>      except (etree.ParseError, AttributeError, ValueError):
>> AttributeError: 'module' object has no attribute 'ParseError'
>> Thread-1483::ERROR::2013-03-04
>> 16:35:27,481::BindingXMLRPC::932::vds::(wrapper) unexpected error
>> 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: 'module' object has no attribute 'ParseError'
>>
>
> 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)?
>

python 2.7 throws ParseError whereas python 2.6 throws SyntaxError. 
Aravinda is sending a fix for it.

Regards,
Bala