Bug 692654

Summary:	selinux enforcing on a reboot
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Mo Morsi <mmorsi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dave Johnson <dajohnso>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.3.1	CC:	cpelland, deltacloud-maint, whayutin
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-31 19:26:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Johnson 2011-03-31 19:14:13 UTC

Description of problem:
After a reboot the web app was giving me a 503 error.  I talked to Morazi who pointed at selinux as the cause which appears to be the case.  aeolus-configure runs 'setenforce 0' but that doesn;t persist across reboots.  Looking at /etc/selinux/config shows it is configured for 'Enforcing'.  

An additional step of fixing the selinux config file to use 'Permissive' mode on future start ups is needed.  As soon as I ran, 'setenforce 0', the web ui was accessible.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 wes hayutin 2011-03-31 19:26:10 UTC

My understanding is that we ship w/ selinux enforcing.. 
Durring dev/test selinux can be in permissive.

Closing.. this is not a bug

Comment 2 wes hayutin 2011-12-08 14:07:55 UTC

perm close