[Users] oVirt 3.2 on CentOS with Gluster 3.3

[Dan Kenigsberg]

On Mon, Mar 11, 2013 at 06:09:56AM -0400, Balamurugan Arumugam wrote:
> 
> 
> ----- Original Message -----
> > From: "Dan Kenigsberg" <danken at redhat.com>
> > To: "Balamurugan Arumugam" <barumuga at redhat.com>
> > Cc: "Rob Zwissler" <rob at zwissler.org>, users at ovirt.org, "Aravinda VK" <avishwan at redhat.com>, "Ayal Baron"
> > <abaron at redhat.com>
> > Sent: Sunday, March 10, 2013 1:04:50 PM
> > Subject: Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3
> > 
> > On Wed, Mar 06, 2013 at 02:34:10PM +0530, Balamurugan Arumugam wrote:
> > > 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 at redhat.com> 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
> > 
> > Bala, Aravinda, I have not seem a vdsm patch adding an explicit
> > dependency on the correct gluster-cli version. Only a change for for
> > this ParseError issue http://gerrit.ovirt.org/#/c/12829/
> > 
> > Is there anything blocking this? I would really like to clear this
> > hurdle quickly.
> > 
> 
> Dan, we are working out locally to resolve of setting up glusterfs version for vdsm-gluster.  We will submit new patch soon.

I do not understand the complexity of this. Why not simply add

   Requires: glusterfs >= 3.4.0

?