Bug 1293267

Summary:	Ansible installation needs to handle SELinux booleans when installing containerized env
Product:	OpenShift Container Platform	Reporter:	Jianwei Hou <jhou>
Component:	Installer	Assignee:	Andrew Butcher <abutcher>
Status:	CLOSED ERRATA	QA Contact:	Ma xiaoqiang <xiama>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	aos-bugs, bleanhar, cryan, jokerman, mmccomas, xtian
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:	2016-01-27 19:43:27 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 Jianwei Hou 2015-12-21 09:29:14 UTC

Description of problem:
On AEP the necessary SELinux booleans are turned off by default, for example: virt_sandbox_use_fusefs, virt_use_nfs. The ansible installation did not handle the installation of storage modules because the packages are already present on AEP, therefore the SELinux booleans are also not dealt with.

Version-Release number of selected component (if applicable):
openshift v3.1.1.0
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2

How reproducible:
Always

Steps to Reproduce:
1. Run ansible installation
2. Create pods with nfs volume, found that all pods end up in error state. Inspected the pods and found it was caused by "virt_use_nfs -> off"

Actual results:


Expected results:
If possible, ansible installation should handle that.

Additional info:

Comment 2 Jianwei Hou 2016-01-08 02:32:02 UTC

The bug is fixed with the PR. Mark as verified.

Comment 4 errata-xmlrpc 2016-01-27 19:43:27 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://access.redhat.com/errata/RHBA-2016:0075