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 867354 - Configure the selinux sanlock_use_nfs boolean
Summary: Configure the selinux sanlock_use_nfs boolean
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Federico Simoncelli
QA Contact: Dafna Ron
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-17 11:15 UTC by Federico Simoncelli
Modified: 2022-07-09 05:40 UTC (History)
10 users (show)

Fixed In Version: vdsm-4.9.6-39.0
Doc Type: Bug Fix
Doc Text:
Previously, VDSM did not correctly configure SELinux to work correctly with sanlock on NFS shares, which interfered with the workings of the Storage Pool Manager. Now, VDSM automatically sets the boolean required for sanlock to use NFS shares.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:12:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

Description Federico Simoncelli 2012-10-17 11:15:32 UTC
Description of problem:
VDSM should configure the selinux sanlock_use_nfs boolean.


Version-Release number of selected component (if applicable):
vdsm-4.9.6-38.0.el6_3


How reproducible:
100%

Steps to Reproduce:
1. Connect to a nfs pool
  
Actual results:
The following warning messages appear in /var/log/messages:

denied  { open } for comm="sanlock" name="ids" dev=0:1f scontext=system_u:system_r:sanlock_t:s0-s0:c0.c1023 tcontext=system_u:object_r:nfs_t:s0 tclass=file
denied  { open } for comm="sanlock" name="leases" dev=0:1c scontext=system_u:system_r:sanlock_t:s0-s0:c0.c1023 tcontext=system_u:object_r:nfs_t:s0 tclass=file


Expected results:
No warnings in the messages.

Additional info:
An upstream patch has been committed here:


Author: Federico Simoncelli <fsimonce>
Date:   Thu Sep 27 08:31:08 2012 -0400

    setup: configure selinux for sanlock on nfs

http://gerrit.ovirt.org/8255

Comment 5 Daniel Paikov 2012-11-27 15:07:09 UTC
Checked on 4.9.6-44

Comment 7 errata-xmlrpc 2012-12-04 19:12:51 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


Note You need to log in before you can comment on or make changes to this bug.