Bug 1038281

Summary: Do not turn off selinux by default on the foreman server
Product: Red Hat OpenStack Reporter: Crag Wolfe <cwolfe>
Component: openstack-foreman-installerAssignee: Jason Guiditta <jguiditt>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: breeler, ddomingo, hateya, jguiditt, morazi, rhos-maint, yeylon
Target Milestone: rcKeywords: OtherQA, Rebase
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-foreman-installer-0.0.24-1.el6ost Doc Type: Bug Fix
Doc Text:
Previously, the foreman_server.sh script contained a command that explicitly disabled SELinux. This posed a security risk, as the command disabled SELinux even if the user had it enabled previously. This update removes the command that disables SELinux. As a result, Foreman now installs the appropriate policy if the user already has SELinux enabled.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 00:41:08 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:

Description Crag Wolfe 2013-12-04 19:32:24 UTC
Running the openstack foreman installer, foreman_server.sh, causes selinux to be turned off.  This should be removed.  Instead, the user should decide for themselves whether to run selinux and whether or not to install the foreman-selinux rpm (which is already in the RHOS channel).

Comment 2 Jason Guiditta 2013-12-05 21:24:48 UTC
Merged upstream

https://github.com/redhat-openstack/astapor/pull/70

Comment 6 Omri Hochman 2013-12-16 15:54:48 UTC
Verified with openstack-foreman-installer-0.0.25-1.el6ost.noarch
(Puddle 2013-12-12.1)

After foreman_server.sh installation the SELINUX is Enabled.

[root@foreman-server ~]# getenforce 
Enforcing

Comment 8 errata-xmlrpc 2013-12-20 00:41:08 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html