[Users] oVirt 3.2 on CentOS with Gluster 3.3

Wed Mar 6 04:10:27 EST 2013

On Wed, Mar 06, 2013 at 02:04:29PM +0530, Shireesh Anjal wrote:
> On 03/05/2013 06:08 AM, 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
> 
> oVirt 3.2 needs a newer (3.4.0) version of glusterfs, which is
> currently in alpha and hence not available in stable repositories.
> http://bits.gluster.org/pub/gluster/glusterfs/3.4.0alpha/

Shireesh, this should be specifed in vdsm.spec - please patch both
master and ovirt-3.2 branches.

Beyond that, there's a problem of Python 2.6 missing ParseError.

> 
> This issue has been reported multiple times now, and I think it
> needs an update to the oVirt 3.2 release notes. Have added a note to
> this effect at:
> http://www.ovirt.org/OVirt_3.2_release_notes#Storage
> 
> >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'
> >
> >Which corresponds to the following in the engine.log:
> >
> >2013-03-04 16:34:46,231 INFO
> >[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
> >(QuartzScheduler_Worker-86) START,
> >GlusterVolumesListVDSCommand(HostName = xor-q-virt01, HostId =
> >b342bf4d-d9e9-4055-b662-462dc2e6bf50), log id: 987aef3
> >2013-03-04 16:34:46,365 ERROR
> >[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
> >(QuartzScheduler_Worker-86) Failed in GlusterVolumesListVDS method
> >2013-03-04 16:34:46,366 ERROR
> >[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
> >(QuartzScheduler_Worker-86) Error code unexpected and error message
> >VDSGenericException: VDSErrorException: Failed to
> >GlusterVolumesListVDS, error = Unexpected exception
> >2013-03-04 16:34:46,367 ERROR
> >[org.ovirt.engine.core.vdsbroker.VDSCommandBase]
> >(QuartzScheduler_Worker-86) Command GlusterVolumesListVDS execution
> >failed. Exception: VDSErrorException: VDSGenericException:
> >VDSErrorException: Failed to GlusterVolumesListVDS, error = Unexpected
> >exception
> >2013-03-04 16:34:46,369 INFO
> >[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
> >(QuartzScheduler_Worker-86) FINISH, GlusterVolumesListVDSCommand, log
> >id: 987aef3
> >2013-03-04 16:34:46,370 ERROR
> >[org.ovirt.engine.core.bll.gluster.GlusterManager]
> >(QuartzScheduler_Worker-86) Error while refreshing Gluster lightweight
> >data of cluster qa-cluster1!:
> >org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException:
> >org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> >VDSGenericException: VDSErrorException: Failed to
> >GlusterVolumesListVDS, error = Unexpected exception
> >	at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:168)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.gluster.GlusterManager.runVdsCommand(GlusterManager.java:258)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.gluster.GlusterManager.fetchVolumes(GlusterManager.java:454)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.gluster.GlusterManager.fetchVolumes(GlusterManager.java:440)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.gluster.GlusterManager.refreshVolumeData(GlusterManager.java:411)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.gluster.GlusterManager.refreshClusterData(GlusterManager.java:191)
> >[engine-bll.jar:]
> >	at org.ovirt.engine.core.bll.gluster.GlusterManager.refreshLightWeightData(GlusterManager.java:170)
> >[engine-bll.jar:]
> >	at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> >[:1.7.0_09-icedtea]
> >	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >[rt.jar:1.7.0_09-icedtea]
> >	at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09-icedtea]
> >	at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:60)
> >[engine-scheduler.jar:]
> >	at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz-2.1.2.jar:]
> >	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
> >[quartz-2.1.2.jar:]
> >
> >And, long story short, the gluster integration with oVirt does not
> >work.  As per Vijay Bellur's comments at
> >http://list-archives.org/2012/12/27/users-ovirt-org/continuing-my-ovirt-3-2-nightlies-queste/f/7132789998
> >this is due to a difference in the XML formatting output by gluster
> >vs. what is expected by VDSM, and is fixed in Gluster 3.4, which is
> >currently in alpha pre-release.
> >
> >So my question is, was oVirt v3.2 released with a dependency on a
> >version of Gluster that is in alpha, or is there another workaround or
> >fix for this?
> >
> >Rob
> >_______________________________________________
> >Users mailing list
> >Users at ovirt.org
> >http://lists.ovirt.org/mailman/listinfo/users
> 

> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users