Bug 1040145

Summary:	oo-accept-node alerts on valid ruby193-mcollective selinux contexts
Product:	OpenShift Online	Reporter:	Sten Turpin <sten>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.x
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-10 20:18:20 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:

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 ***