Bug 1293267 - Ansible installation needs to handle SELinux booleans when installing containerized env
Summary: Ansible installation needs to handle SELinux booleans when installing contain...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Andrew Butcher
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-21 09:29 UTC by Jianwei Hou
Modified: 2016-07-04 00:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-27 19:43:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0075 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-01-28 00:42:22 UTC

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


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