[Users] oVirt 3.2 on CentOS with Gluster 3.3

[Dan Kenigsberg]

On Wed, Mar 13, 2013 at 04:10:56PM -0400, Federico Simoncelli wrote:
> ----- Original Message -----
> > From: "Dan Kenigsberg" <danken at redhat.com>
> > To: "Balamurugan Arumugam" <barumuga at redhat.com>, "Federico Simoncelli" <fsimonce at redhat.com>, "Mike Burns"
> > <mburns at redhat.com>
> > Cc: "Rob Zwissler" <rob at zwissler.org>, users at ovirt.org, arch at ovirt.org, "Aravinda VK" <avishwan at redhat.com>, "Ayal
> > Baron" <abaron at redhat.com>
> > Sent: Wednesday, March 13, 2013 9:03:39 PM
> > Subject: Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3
> > 
> > On Mon, Mar 11, 2013 at 12:34:51PM +0200, Dan Kenigsberg wrote:
> > > On Mon, Mar 11, 2013 at 06:09:56AM -0400, Balamurugan Arumugam
> > > 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
> > 
> > Ok, both issues have fixes which are in the ovirt-3.2 git branch.
> > I believe this deserves a respin of vdsm, as having an undeclated
> > requirement is impolite.
> > 
> > Federico, Mike, would you take care for that?
> 
> Since we're at it... I have the feeling that this might be important
> enough to be backported to 3.2 too:
> 
> http://gerrit.ovirt.org/#/c/12178/

Yes, it is quite horrible. Could you include that, too?