----- Original Message -----
> From: "Laszlo Hornyak" <lhorn...@redhat.com>
> To: vdsm-devel@lists.fedorahosted.org
> Sent: Monday, August 27, 2012 11:29:07 AM
> Subject: [vdsm] sanlock and vdsm on rhel 6.3
> 
> hi,
> 
> If I understand correctly, the latest vdsm requires sanlock 2.3-3 on
> rhel
> http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm.spec.in;h=ce73f6e08b472e5f4e65ecc87bf6099938b0a255;hb=HEAD
> while on fedora version 2.4 is required. I guess the reason is that
> sanlock 2.4 is not packaged in rhel yet, but the problem is that it
> seems vdsm is built on a functionality in inq_lockspace that is new
> in sanlock 2.4, so it does not accept the wait=True parameter that
> vdsm passes over in safelease.py
> (http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/storage/safelease.py;h=551dda5c9989849b7029b719dd4b556371baa6ae;hb=HEAD#l170)
> and the whole task fails.
> (see
> http://git.fedorahosted.org/cgit/sanlock.git/tree/python/sanlock.c?id=acd0d65a072c281de621e5c6dcc92b0e355f3232)
> 
> I did not dare to remove the wait=True, it looks like a serious
> functionality change for me that would probably break something in
> vdsm. How can I solve this problem?

sanlock 2.3-3 in rhel6.3 already contains the patch that you need.

-- 
Federico
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to