Bug 1040145 - oo-accept-node alerts on valid ruby193-mcollective selinux contexts
Summary: oo-accept-node alerts on valid ruby193-mcollective selinux contexts
Keywords:
Status: CLOSED DUPLICATE of bug 1038237
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 20:07 UTC by Sten Turpin
Modified: 2015-05-14 23:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-10 20:18:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sten Turpin 2013-12-10 20:07:51 UTC 
Description of problem: oo-accept-node alerts on valid selinux contexts for ruby193-mcollective

Version-Release number of selected component (if applicable):
openshift-origin-node-util-1.17.4-1.el6oso.noarch


How reproducible:
always

Steps to Reproduce:
1. allow Zabbix to restart ruby193-mcollective (e.g. stop it)
2. run oo-accept-node


Actual results:
FAIL: SELinux context for ruby193-mcollective is incorrect

Expected results:
PASS

Additional info:
The SELinux context that was flagged on was: 
system_u:system_r:zabbix_agent_t:s0
due to Mcollective failing and being re-started by Zabbix via an automated heal action. This is a valid context for our use.
Comment 1 Jhon Honce 2013-12-10 20:18:20 UTC 

*** This bug has been marked as a duplicate of bug 1038237 ***
Note You need to log in before you can comment on or make changes to this bug.