Bug 692654 - selinux enforcing on a reboot
Summary: selinux enforcing on a reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: beta
Assignee: Mo Morsi
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 19:14 UTC by Dave Johnson
Modified: 2012-01-26 12:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-31 19:26:10 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.