Bug 1174776

Summary:	User can not login into the overcloud horizon using the proper credentials
Product:	[Community] RDO	Reporter:	Ami Jeain <ajeain>
Component:	openstack-tripleo	Assignee:	James Slagle <jslagle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shai Revivo <srevivo>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Juno	CC:	chris.brown, srevivo, ukalifon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-18 06:31:57 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:
Embargoed:

Description Ami Jeain 2014-12-16 13:03:21 UTC

Description of problem:


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


How reproducible:

always
Steps to Reproduce:
1. Follow the instructions in: https://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack (VM setup)
2. follow: https://openstack.redhat.com/Deploying_an_RDO_Overcloud_with_Instack and deploy with instack-virt-setup, instack-install-undercloud and instack-deploy-overcloud
3. try to login into the overcloud Horizon (of course, using ssh tunneling)

Actual results:

upon hitting Sign In, you will get:
An error occurred authenticating. Please try again later.

Expected results:

user is able to login fine
Additional info:

No useful info is found in the logs of either keystone or httpd. To troubleshoot the problem, we used the CLI and the REST API (with curl) and we could see that we can create users and get a token for them - but in horizon there is no way to log in with them.
Also:

running the following command on the overcloud controller:

# openstack-status |grep dashboard

gives:

openstack-dashboard:                    uncontactable

Comment 2 James Slagle 2014-12-16 14:51:36 UTC

We have the local_settings misconfigured. Can you try the following on your
overcloud controller as root and see if this fixes it?


/bin/cp /etc/horizon/local_settings.py /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py
sed -i 's#^STATIC_ROOT.*#STATIC_ROOT = "'/usr/share/openstack-dashboard/static'"#' /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py
systemctl restart httpd

Comment 3 James Slagle 2014-12-16 14:53:07 UTC

> Also:
> 
> running the following command on the overcloud controller:
> 
> # openstack-status |grep dashboard
> 
> gives:
> 
> openstack-dashboard:                    uncontactable

For this piece, openstack-status does a curl against localhost for the dashboard test. That
does not seem to be working in the TripleO case, I'd assume because of the HA
setup and the fact that httpd is not bound to localhost.

I wonder if this works in an HA setup deployed by Foreman?

Comment 4 James Slagle 2014-12-16 16:27:14 UTC

this is fixed in a new brew build of openstack-tripleo-image-elements:
https://brewweb.devel.redhat.com/buildinfo?buildID=404391
openstack-tripleo-image-elements-0.8.10-11.el7ost

You would need to update to this build on your undercloud, and then rebuild the overcloud control image.

Comment 5 James Slagle 2014-12-16 16:28:37 UTC

(In reply to James Slagle from comment #4)
> this is fixed in a new brew build of openstack-tripleo-image-elements:
> https://brewweb.devel.redhat.com/buildinfo?buildID=404391
> openstack-tripleo-image-elements-0.8.10-11.el7ost
> 
> You would need to update to this build on your undercloud, and then rebuild
> the overcloud control image.

To rebuild the overcloud-control image, remove or mv the old one out of the way on the undercloud

cd /home/stack
rm -rf overcloud-control*

Re-run image build script:

instack-build-images

Load image into glance via this script:

instack-prepare-for-overcloud

Comment 9 Christopher Brown 2017-06-17 16:59:47 UTC

This has been fixed for years so can be closed.