This regression was introduced by (my) patch:

Which was recently merged to master.

You can see how updateTimestamp() is implemented at:, line 83. (A dummy/blank implementation would not work).

There's several approaches to solve this, I think the correct way would be
to make updateTimestamp a class method of the BindingXMLRPC class, and change
the calls from im_self to BindingXMLRPC.updateTimestamp. That way it doesn't
matter which method wrapApiMethod wraps, or what class defined the method,
it'll 'just work'.

I'll send a patch ASAP.

Assaf Muller, Cloud Networking Engineer 
Red Hat 

----- Original Message -----
From: "Balamurugan Arumugam" <>
To: "Nir Soffer" <>
Cc: "VDSM Project Development" <>
Sent: Tuesday, January 7, 2014 3:40:53 PM
Subject: [vdsm] gluster verbs are broken due to missing updateTimestamp()


I see vdsm master is broken wrt gluster verbs.  When I run any gluster verbs, 
it errors out

Traceback (most recent call last):
File "/usr/share/vdsm/", line 941, in wrapper
AttributeError: 'GlusterApi' object has no attribute 'updateTimestamp'

I added a dummy updateTimestamp() in gluster.api.GlusterApi which resolves the 
issue, but I am not sure whether its correct or not.

Could you provide some info on updateTimestamp() and whether its applicable to 
gluster module?

vdsm-devel mailing list
vdsm-devel mailing list

Reply via email to