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 634357 - fence_scsi fails to unfence with selinux AVC denials
Summary: fence_scsi fails to unfence with selinux AVC denials
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.0
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 532805 636489
TreeView+ depends on / blocked
 
Reported: 2010-09-15 21:37 UTC by Ryan O'Hara
Modified: 2012-11-23 21:07 UTC (History)
5 users (show)

Fixed In Version: selinux-policy-3.7.19-55.el6
Doc Type: Bug Fix
Doc Text:
When the cluster was configured to use fence_scsi, running the cman startup script or using the "fence_node -U <nodename>" command failed. These updated selinux-policy packages contain updated SELinux rules and add the security file context for the /var/lib/cluster directory, which allows the cluster with fence_scsi enabled to work properly.
Clone Of:
Environment:
Last Closed: 2011-05-19 11:55:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Example config for 3-node RHEL6 cluster w/fence_scsi (930 bytes, application/octet-stream)
2010-09-15 21:37 UTC, Ryan O'Hara 		no flags Details
AVC denials for fence_scsi unfencing in permissive mode. (7.67 KB, text/plain)
2010-09-16 22:29 UTC, Ryan O'Hara 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0526 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2011-05-19 09:37:41 UTC

Description Ryan O'Hara 2010-09-15 21:37:07 UTC 
Created attachment 447574 [details]
Example config for 3-node RHEL6 cluster w/fence_scsi

Description of problem:

The fence_scsi agent fails at cman startup when selinux is enabled. When the cman init script starts, it will call 'fence_node -U <nodename>'. This is referred to as unfencing. If an unfence section exists in cluster.conf, the agent will be called with appropriate parameters (typically "action=on").

With fence_scsi (perl script), we see the following AVCs:

type=AVC msg=audit(1284585609.699:38506): avc:  denied  { write } for  pid=12562 comm="fence_scsi" name="cluster" dev=dm-0 ino=523912 scontext=unconfined_u:system_r:fenced_t:s0 tcontext=system_u:object_r:var_lib_t:s0 tclass=dir

type=SYSCALL msg=audit(1284585609.699:38506): arch=c000003e syscall=2 
success=no exit=-13 a0=1cd6550 a1=241 a2=1b6 a3=309291dd10 items=0 ppid=12546 pid=12562 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts2 ses=386 comm="fence_scsi" exe="/usr/bin/perl" subj=unconfined_u:system_r:fenced_t:s0 key=(null)


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

selinux-policy-3.7.19-54.el6.noarch
fence-agents-3.0.12-8.el6.x86_64
cman-3.0.12-23.el6.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Configure cluster to use fence_scsi.
2. Run 'service cman start' or 'fence_node -U <nodename>', where node is the local node's name.
  
Actual results:

AVC denials (see above).

Expected results:

- no AVCs.
- key registered with device(s)
- key file created in /var/lib/cluster/fence_scsi.key
- output written to logfile, if configured.

Additional info:

I will attach a same cluster.conf to show how fence_scsi is configured.
Comment 2 Daniel Walsh 2010-09-16 10:33:14 UTC 
Who owns the directory /var/lib/cluster?
Comment 3 Daniel Walsh 2010-09-16 11:10:01 UTC 
Are there any other directories under /var/lib or /var/run that we do not know about?
Comment 4 Miroslav Grepl 2010-09-16 11:11:29 UTC 
Dan,

this directory is owned by cman. I am able to reproduce it. So I would add a
new label for this dir

cluster_var_lib_t

and allow rhcs domains to manage this directory.
Comment 6 Miroslav Grepl 2010-09-16 15:58:35 UTC 
Fixed in selinux-policy-3.7.19-55.el6.noarch.
Comment 7 Ryan O'Hara 2010-09-16 22:29:56 UTC 
Created attachment 447856 [details]
AVC denials for fence_scsi unfencing in permissive mode.

I ran fence_scsi (unfence) again, this time in permissive mode. Here are the AVC denials I see when running in permissive mode, with the same policy as before.
Comment 8 Miroslav Grepl 2010-09-17 07:48:20 UTC 
Ryan,
could you test it with selinux-policy-3.7.19-55.el6.noarch policy which has a fix for that. Thanks.
Comment 9 Ryan O'Hara 2010-09-17 20:17:20 UTC 
(In reply to comment #8)
> Ryan,
> could you test it with selinux-policy-3.7.19-55.el6.noarch policy which has a
> fix for that. Thanks.

Yes. I just finished testing. After installing the updated policy, I did the following:

% setenforce 1
% fence_tool -Uvv <nodename>

Checking the audit.log, the last entry I see is for 'setenforce'. Seems that fence_scsi no longer generates any AVC denials. Excellent.
Comment 13 Jaromir Hradilek 2010-10-14 12:11:26 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:
When the cluster was configured to use fence_scsi, running the cman startup script or using the "fence_node -U <nodename>" command failed. These updated selinux-policy packages contain updated SELinux rules and add the security file context for the /var/lib/cluster directory, which allows the cluster with fence_scsi enabled to work properly.
Comment 16 errata-xmlrpc 2011-05-19 11:55:10 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0526.html
Note You need to log in before you can comment on or make changes to this bug.