Bug 1331040

Summary:	Can't retrieve list of project from Horizon (so can't spawn VM from Horizon)
Product:	Red Hat OpenStack	Reporter:	Alexandre Maumené <amaumene>
Component:	python-django-horizon	Assignee:	Itxaka <iserrano>
Status:	CLOSED NOTABUG	QA Contact:	Ido Ovadia <iovadia>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	aortega, athomas, mcornea, mrunge, srevivo
Target Milestone:	---	Keywords:	ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-22 08:56:52 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 Alexandre Maumené 2016-04-27 14:01:59 UTC

Description of problem:
I'm working on a deployment with a Active Directory configured as
Keystone's Identity driver. The assignment driver is configured to use MySQL and
we are using keystone v2. Pretty much everything is working great in
CLI, I'm able to create tenant, assign user to it, create network,
spawn VM, etc...

But there is an annoying issue for the customer when using Horizon.
When you log in, the "Project" menu in top right corner is empty and in
fact Horizon is not able at all to retrieve the list of projects (so
it's impossible to spawn a VM from it since you have to choose in which project you want to spawn it).

Version-Release number of selected component (if applicable):
python-django-horizon-2015.1.2-4.el7ost.noarch
python-keystone-2015.1.2-2.el7ost.noarch
openstack-keystone-2015.1.2-2.el7ost.noarch

How reproducible:
Every time

Steps to Reproduce:
0. Get an ActiveDirectory with users in it
1. Switch Identity driver of Keystone to LDAP
2. Setup Assignment driver of Keystone to SQL
3. Login to Horizon

Actual results:
Unable to list projects through Horizon

Expected results:
Able to list projects through Horizon

Additional info:

Comment 2 Matthias Runge 2016-04-27 14:09:20 UTC

What kind of tokens do you use and how are sessions set up?

Comment 3 Alexandre Maumené 2016-04-27 14:39:45 UTC

I'm not sure to understand your questions, but I didn't change anything related to tokens and sessions.

Anyway for tokens:
[token]
expiration = 3600
provider = keystone.token.providers.uuid.Provider
driver = keystone.token.persistence.backends.sql.Token

For sessions:
SESSION_ENGINE = "django.contrib.sessions.backends.cache"

Comment 4 Matthias Runge 2016-04-27 16:04:08 UTC

Did you horizon to use keystone v3 or v2?
Are you using hierarchical projects?

AD is mostly irrelevant here, since Horizon talks to keystone.

Comment 5 Alexandre Maumené 2016-04-28 01:22:34 UTC

We use keystone v2 and no hierarchical projects. As I said nothing else has been changed from the OSP-d deployment.

Not sure AD is not relevant since it's after this switch that the problem appears. (it may also be a side effect).

Comment 6 Itxaka 2016-04-28 08:36:24 UTC

What is the output of keystone tenant-list in the CLI? Does it return the expected output of tenants?


Can you attach some logs of horizon to see if there is any errors? Do you get any errors on the UI?

Unfortunately I cannot reproduce the environment locally, devstack+ldap fails to deploy correctly so Im a bit blind on this, so as much info and logs as possible would be appreciated.