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 906590 - Sanlock mishandles locks for paused domains in libvirt
Summary: Sanlock mishandles locks for paused domains in libvirt
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sanlock
Version: 6.3
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-31 23:40 UTC by Michael Rodrigues
Modified: 2016-04-18 06:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-30 14:08:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Rodrigues 2013-01-31 23:40:51 UTC 
Description of problem:

Sanlock does not properly lock filesystems of paused VMs, allowing another domain to use the same filesystem (shared Logical Volume on Fibre Channel) and boot without a lock error.


Version-Release number of selected component (if applicable):

libvirt-lock-sanlock.x86_64        0.9.10-21.el6_3.8           @updates         
sanlock.x86_64                     2.3-1.el6                   @base            
sanlock-devel.x86_64               2.3-1.el6                   @base            
sanlock-lib.x86_64                 2.3-1.el6                   @base 


How reproducible:

100%


Steps to Reproduce:

1. Share an LVM volume group between two hosts running libvirt.
2. Create a LV-based VM on node 1.
3. Start the VM on node 1.
4. Migrate the VM to node 2. Node 1's copy is now shutdown, node 2's should be running.
5. Shutdown node 2
6. Start node 1
7. Pause node 1
8. Start node 2
9. Pause node 2
10. Start node 1

  
Actual results:

Sanlock throws no lock errors on any of the above steps. It will only throw a lock error if I try to start one while the other is running.

Expected results:

According to the libvirt-users mailing list, when I pause node 1 in step 7, it should record a lease version number. When I resume in step 10, the version should mismatch due to step 8 and throw an error.

Additional info:

https://www.redhat.com/archives/libvirt-users/2013-January/msg00109.html
Comment 3 David Teigland 2013-02-01 20:35:07 UTC 
Hi, sanlock is only tested and supported as part of the RHEV product, but I'd still like to investigate whether there's a bug here or not.  To do that, I'll need you to:

1. Try this on Fedora 18, or RHEL 6.4 (once that's available).
2. Show us your specific configuration files, and the exact commands you are running in sequence.
3. Collect debugging information from sanlock and libvirt.
For sanlock, run the command "sanlock log_dump > log.txt" from each node.
I'm not sure what libvirt info to collect.
Comment 4 Michael Rodrigues 2013-02-01 20:42:39 UTC 
Hi,

I wasn't exactly sure where to post the bug, just directed to by the user list.

I can do all of this on Fedora 18 but I don't have access to RHEL. Is it still worth the trouble for me to do if I can't provide the relevant RHEL information? I'm doing all of my testing on CentOS 6.3 currently.

Thanks for your input.
Comment 5 David Teigland 2013-02-01 20:46:42 UTC 
Fedora 18 would be the best way to test this.
Comment 7 RHEL Program Management 2013-02-07 06:47:09 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 8 David Teigland 2015-09-30 14:08:35 UTC 
There was never a specific issue identified.
Note You need to log in before you can comment on or make changes to this bug.