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 801493 - Please create policy for pacemaker (runs as initrc_t)
Summary: Please create policy for pacemaker (runs as initrc_t)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 768522 832330 848613 915151 1003613
TreeView+ depends on / blocked
 
Reported: 2012-03-08 16:27 UTC by Jaroslav Kortus
Modified: 2014-06-17 14:07 UTC (History)
4 users (show)

Fixed In Version: selinux-policy-3.7.19-160.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 848613 915151 (view as bug list)
Environment:
Last Closed: 2013-02-21 08:34:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Working policy module (2.24 KB, application/x-gzip)
2013-01-04 11:23 UTC, Vladislav Bogdanov 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0314 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2013-02-20 20:35:01 UTC

Description Jaroslav Kortus 2012-03-08 16:27:47 UTC 
Description of problem:
pacemaker (possible rgmanager replacement) does not have any policy defined and starts in initrc_t.

Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-139.el6.noarch


How reproducible:
always

Steps to Reproduce:
1. service pacemaker start
2.
3.
  
Actual results:
wrong context

Expected results:
pacemaker's own context for all daemons with proper permissions (TBD)

Additional info:
Comment 2 Miroslav Grepl 2012-03-09 10:24:59 UTC 
Jaroslav,
so is it going to work as rgmanager? Probably you could try to treat it with rgmanager using

$ chcon -t rgmanager_exec_t /usr/sbin/pacemakerd

We added pacemaker policy to Fedora but if this policy ends up unconfined as rgmanager we will treat it with rgmanager.
Comment 7 RHEL Program Management 2012-07-10 08:20:21 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 RHEL Program Management 2012-07-11 01:55:22 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 15 Andrew Beekhof 2012-12-21 01:29:24 UTC 
Stupid question, have we tried it with some cluster services (like an IP address) configured?
Comment 17 Vladislav Bogdanov 2013-01-04 11:23:57 UTC 
Created attachment 672367 [details]
Working policy module

This one can be considered as a starting point, because I use it with corosync2 but not with cman.
Please look at thread
http://comments.gmane.org/gmane.linux.highavailability.pacemaker/15817
for more details.
Comment 18 errata-xmlrpc 2013-02-21 08:34:48 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/RHBA-2013-0314.html
Comment 19 Andrew Beekhof 2013-02-22 07:43:58 UTC 
How come this got closed?
Can we get some feedback on the patch in comment #17 please?

A cluster that can't control resources isn't very useful.
Do we need to clone this into 6.4 or something?
Comment 20 Miroslav Grepl 2013-02-22 09:24:21 UTC 
This bug was about a new policy which we added. Please open a new one. Thank you.
Note You need to log in before you can comment on or make changes to this bug.