[ovirt-users] Re: glusterevents daemon fails after upgrade from 4.2.8 to 4.3

[Aravinda]

Looks like Python 3 porting issue. I will work on the fix soon. Thanks


On Thu, 2019-02-07 at 13:27 +0530, Sahina Bose wrote:
> +Aravinda Vishwanathapura Krishna Murthy can you take a look? oVirt
> 4.3 has Gluster 5
> 
> On Wed, Feb 6, 2019 at 7:35 PM Edward Berger 
> wrote:
> > I upgraded some nodes from 4.28 to 4.3 and now when I look at the
> > cockpit "services"
> > tab I see a red failure for Gluster Events Notifier and clicking
> > through I get these messages below.
> > 
> > 14:00
> > glustereventsd.service failed.
> > systemd
> > 14:00
> > Unit glustereventsd.service entered failed state.
> > systemd
> > 14:00
> > glustereventsd.service: main process exited, code=exited,
> > status=1/FAILURE
> > systemd
> > 14:00
> > ValueError: Attempted relative import in non-package
> > glustereventsd
> > 14:00
> > from .eventsapiconf import (LOG_FILE,
> > glustereventsd
> > 14:00
> > File "/usr/libexec/glusterfs/events/utils.py", line 29, in 
> > glustereventsd
> > 14:00
> > import utils
> > glustereventsd
> > 14:00
> > File "/usr/libexec/glusterfs/events/handlers.py", line 12, in
> > 
> > glustereventsd
> > 14:00
> > import handlers
> > glustereventsd
> > 14:00
> > File "/usr/sbin/glustereventsd", line 24, in 
> > glustereventsd
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct: 
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives: 
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/K6N5EWVRPYRAXBUON2XNJVT5OH42PDEN/
-- 
regards
Aravinda
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7ZNQ4TJTO42YKF44E5QHDLRC7QUERY7Z/

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

[Aravinda]

Hi,

Sent a patch to handle ParseError attribute issue. vdsm still depends on 
newer(3.4) version of glusterfs, but Python ParseError is fixed.

http://gerrit.ovirt.org/#/c/12752/

--
regards
Aravinda

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 dan...@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).

Dan.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users