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 782600 - update sanlock
Summary: update sanlock
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sanlock
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: Haim
URL:
Whiteboard: storage
: 795756 805903 815730 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-17 21:33 UTC by David Teigland
Modified: 2016-04-26 15:21 UTC (History)
11 users (show)

Fixed In Version: sanlock-2.3-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
The sanlock package is being updated with features and fixes needed by vdsm. The sanlock package is shipped for limited usage in the RHEV product. Independent usage, e.g. by libvirt, is considered Technology Preview and is not yet fully supported. In a future release of RHEL we may consider broader support.
Clone Of:
Environment:
Last Closed: 2012-06-20 10:38:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 800588 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHEA-2012:0996 0 normal SHIPPED_LIVE sanlock enhancement update 2012-06-20 14:37:53 UTC

Internal Links: 800588

Description David Teigland 2012-01-17 21:33:05 UTC 
Description of problem:

VDSM requires the latest sanlock release in 6.3

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Suzanne Logcher 2012-02-14 23:28:27 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 Ayal Baron 2012-02-15 15:12:05 UTC 
This has to be in, it is required for proper operation of vdsm in rhel 6.3.
Please reevaluate.
Comment 4 Yaniv Kaul 2012-02-16 10:38:37 UTC 
(In reply to comment #3)
> This has to be in, it is required for proper operation of vdsm in rhel 6.3.
> Please reevaluate.

Then it sounds like a blocker.
Comment 14 David Teigland 2012-02-21 16:36:23 UTC 
*** Bug 795756 has been marked as a duplicate of this bug. ***
Comment 17 David Teigland 2012-03-05 16:28:39 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The sanlock package is being updated with features and fixes needed by vdsm.
Comment 19 David Teigland 2012-05-03 16:53:45 UTC 
*** Bug 815730 has been marked as a duplicate of this bug. ***
Comment 20 David Teigland 2012-05-08 14:09:54 UTC 
*** Bug 805903 has been marked as a duplicate of this bug. ***
Comment 21 David Teigland 2012-05-10 16:33:04 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-The sanlock package is being updated with features and fixes needed by vdsm.+The sanlock package is being updated with features and fixes needed by vdsm.  The sanlock package is shipped for limited usage in the RHEV product.  Independent usage, e.g. by libvirt, is considered Technology Preview and is not yet fully supported.  In a future release of RHEL we may consider broader support.
Comment 22 Leonid Natapov 2012-05-24 09:10:57 UTC 
tested with sanlock-2.2-1.el6.x86_64 as part of the tests of preintegration ticket https://engineering.redhat.com/trac/preint/ticket/682 (storage domain v3)
Comment 23 Federico Simoncelli 2012-05-24 18:44:19 UTC 
The negative flows weren't tested. Currently the sanlock process running as the sanlock user isn't able to kill other processes. A fix has been proposed upstream:

https://fedorahosted.org/pipermail/sanlock-devel/2012-May/000183.html
Comment 29 Federico Simoncelli 2012-05-30 12:06:08 UTC 
I found a small issue with the patch proposed in comment 24: when the host boots (and only during the boot) the init script is called in a fashion that is not acquiring the supplementary groups for root, eg:

# egrep ^Groups /proc/$(pgrep sanlock)/status
Groups:	36 107 179

# service sanlock restart
# egrep ^Groups /proc/$(pgrep sanlock)/status
Groups:	0 1 2 3 4 6 10 36 107 179

I tested the behavior with oVirt and the groups "36 107 179" are enough, anyway we may want to consider to modify the init script with:

-       daemon $prog daemon $SANLOCKOPTS
+       daemon --user root $prog daemon $SANLOCKOPTS

so that runuser acquires the supplementary groups for the sanlock process also during the boot.
Comment 30 Haim 2012-05-30 19:17:08 UTC 
verified sanlock scratch build 2.2.2. 
found several issues related to vdsm, moving to verified.
Comment 33 David Teigland 2012-06-15 14:12:34 UTC 
Did some more checking, and can confirm that x86_64-only is correct.
Comment 35 errata-xmlrpc 2012-06-20 10:38:26 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/RHEA-2012-0996.html
Note You need to log in before you can comment on or make changes to this bug.