RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1084918 - unable to login to horizon - selinux blocks port 5000
Summary: unable to login to horizon - selinux blocks port 5000
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RDO
Classification: Community
Component: openstack-selinux
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ryan Hallisey
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-07 08:58 UTC by Amit Ugol
Modified: 2014-10-23 21:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-23 21:48:24 UTC
Embargoed:

Attachments (Terms of Use)

Description Amit Ugol 2014-04-07 08:58:27 UTC 
Description of problem:
cannot login to horizon with any user. port 5000 is inaccessible.
disabling selinux fixes this. re-enabling it will block it again.

Version-Release number of selected component (if applicable):
list of OpenStack packages installed:
http://pastebin.test.redhat.com/201719

list of selinux-policy packages installed:
selinux-policy-3.12.1-151.el7.noarch
selinux-policy-targeted-3.12.1-151.el7.noarch

uname -a:
Linux puma36.scl.lab.tlv.redhat.com 3.10.0-119.el7.x86_64 #1 SMP Thu Apr 3 11:20:15 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
always

Steps to Reproduce:
1. provision rhel7, update to latest.
2. install packstack
3. perform all-in-one

Actual results:
cannot log in to horizon

Expected results:
!Actual

Additional info:
Horizon log:
2014-04-07 08:19:56,197 18007 DEBUG openstack_auth.backend Authorization Failed: Unable to establish connection to http://10.35.160.81:5000/v2.0/tokens
2014-04-07 08:19:56,197 18007 WARNING openstack_auth.forms Login failed for user "admin".
Comment 1 Ryan Hallisey 2014-04-21 18:33:34 UTC 
I need /var/log/audit/audit.log to debug and fix this problem
Comment 2 Amit Ugol 2014-06-09 11:13:07 UTC 
must have missed it, but I don't think it is relevant anymore. forthermore the servers I tested with have been reprovisioned many times since.
Note You need to log in before you can comment on or make changes to this bug.