Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 838802

Summary:	3.1 - Add config option to enable/disable sanlock
Product:	Red Hat Enterprise Linux 6	Reporter:	Andrew Cathrow <acathrow>
Component:	vdsm	Assignee:	Federico Simoncelli <fsimonce>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.4	CC:	abaron, aburden, acathrow, bazulay, chetan, cpelland, hateya, iheim, ilvovsky, jbiddle, rbalakri, ykaul
Target Milestone:	alpha
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:	vdsm-4.9.6-24.0	Doc Type:	Bug Fix
Doc Text:	SANLock was introduced in Red Hat Enterprise Virtualization 3.1, but there was no option to control the volume leases mechanism. This change provides a vdsm.conf option to enable control of the volume leases, but it is disabled by default.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 19:02:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	843467

Description Andrew Cathrow 2012-07-10 07:58:40 UTC

Create vdsm.conf options to enable/disable sanlock.
Default should be disable.

Comment 4 Federico Simoncelli 2012-07-12 10:00:43 UTC

A patch has been proposed upstream:

commit 2a0acf123c758ad999b0a81dbfbb9cdde03291a1
Author: Federico Simoncelli <fsimonce>
Date:   Wed Jul 11 13:42:37 2012 +0000

    BZ#838802 Config option to enable/disable volume leases
    
    Signed-off-by: Federico Simoncelli <fsimonce>
    Change-Id: I3950be962f89c934f617752bbf1c79c61d400bda

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

Comment 7 Leonid Natapov 2012-07-30 14:17:58 UTC

vdsm-4.9.6-24.0.

Enabling the use_volume_leases generates the following section in the vm's domain xml file:
<lease>
      <lockspace>94e13138-9e52-46be-b50c-4ac0bcec0cf2</lockspace>
      <key>e4854f6c-2b3d-4e71-b339-e2c65c2872d1</key>
      <target path='/dev/94e13138-9e52-46be-b50c-4ac0bcec0cf2/leases' offset='110100480'/>
    </lease>

By default use_volume_leases disbaled.
Disabling the use_volume_leases (use_volume_leases=false) disables it.

Fixed.

Comment 12 errata-xmlrpc 2012-12-04 19:02:23 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1508.html