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

----- Original Message ----- > From: "Dan Kenigsberg" <danken(a)redhat.com&gt; > To: "Balamurugan Arumugam" <barumuga(a)redhat.com&gt;, "Federico Simoncelli" <fsimonce(a)redhat.com&gt;, "Mike Burns" > <mburns(a)redhat.com&gt; > Cc: "Rob Zwissler" <rob(a)zwissler.org&gt;, users(a)ovirt.org, arch(a)ovirt.org, "Aravinda VK" <avishwan(a)redhat.com&gt;, "Ayal > Baron" <abaron(a)redhat.com&gt; > 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/