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 1158115 - Create /usr/libexec/keepalived for scripts
Summary: Create /usr/libexec/keepalived for scripts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: keepalived
Version: 6.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Ryan O'Hara
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks: 1198432
TreeView+ depends on / blocked
 
Reported: 2014-10-28 15:30 UTC by Ryan O'Hara
Modified: 2015-08-25 18:55 UTC (History)
7 users (show)

Fixed In Version: keepalived-1.2.13-5.el6
Doc Type: Enhancement
Doc Text:
Clone Of: 1158113
: 1198432 (view as bug list)
Environment:
Last Closed: 2015-08-25 18:55:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan O'Hara 2014-10-28 15:30:51 UTC
+++ This bug was initially created as a clone of Bug #1158113 +++

The keepalived service lacks SELinux privleges to exec scripts, including tracking cripts and notification scripts. Proposed solution is to create a directory (/usr/libexec/keepalived) where scripts can be stored. This directory will then be labelled such that scipts installed here will have sufficient SELinux privileges.

Note that we will not be installing any scripts in this directory as part of keepalived package itself. User will need to create desired scripts in this directory to avoid AVCs.

Comment 4 John Horne 2014-12-04 13:24:04 UTC
Can I ask what is happening with this?
It says it is a clone of bug #1158113 but that one says it is now closed and Fedora (21/22) has been updated. This specific request is for RHEL 6 (and I see the same problem with 7 as well).
So are RHEL 6/7 going to be updated as well?

Comment 6 Ryan O'Hara 2015-03-03 20:09:55 UTC
Jan, does this still affect TripleO HA deployments? I think you brought this to my attention originally. Thanks.

Comment 9 Giulio Fidente 2015-03-04 09:56:51 UTC
hi Ryan, the request comes from https://bugzilla.redhat.com/show_bug.cgi?id=1145886

It's not a problem related to tripleo in particular, it is a more general issue we're trying to solve I think where keepalived needs to have permissions to run scripts so we set in the policy a special location where the scripts should go.

Comment 11 Ryan O'Hara 2015-03-04 14:21:21 UTC
(In reply to Giulio Fidente from comment #9)
> hi Ryan, the request comes from
> https://bugzilla.redhat.com/show_bug.cgi?id=1145886
> 
> It's not a problem related to tripleo in particular, it is a more general
> issue we're trying to solve I think where keepalived needs to have
> permissions to run scripts so we set in the policy a special location where
> the scripts should go.

I completely agree.


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