Bug 1169221

Summary: [SELinux] [Nagios] - Nagios plugins does not work when selinux is enabled on the system.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: nagios-server-addonsAssignee: Timothy Asir <tjeyasin>
Status: CLOSED ERRATA QA Contact: Stanislav Graf <sgraf>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.0CC: asrivast, dpati, knarra, pprakash, rnachimu, sabose, sgraf, vagarwal
Target Milestone: ---Keywords: TestBlocker
Target Release: RHGS 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-23.el7_1.8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-29 05:27:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1113481, 1123574, 1198436, 1198439, 1201054, 1219499, 1222493    
Bug Blocks: 1202842, 1212796    

Description RamaKasturi 2014-12-01 04:49:43 UTC 
Description of problem:
when selinux is enabled on RHS/RHSC node cluster services gives the status as "Null" and cluster status gives status information as "127, plugin code out of bound error".

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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Nagios does not work when selinux is enabled on the system.

Expected results:
Nagios should work seamlessly when selinux is disabled/enabled. 

Additional info:
Comment 7 Dusmant 2015-05-19 09:03:24 UTC 
This bug has to be fixed for both RHEL 6.6 and RHEL 7.1
Comment 12 Stanislav Graf 2015-06-24 19:38:30 UTC 
All plugins works as expected.

I had following booleans status on nagios server node:
nagios_run_pnp4nagios --> on
nagios_run_sudo --> on

and following on monitored node:
nagios_run_pnp4nagios --> off
nagios_run_sudo --> on

--> VERIFIED
Comment 14 errata-xmlrpc 2015-07-29 05:27:03 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.

https://rhn.redhat.com/errata/RHEA-2015-1494.html