Bug 1185960

Summary:	problems with puppet-keystone LDAP support
Product:	[Community] RDO	Reporter:	Rich Megginson <rmeggins>
Component:	openstack-puppet-modules	Assignee:	Ivan Chavero <ichavero>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Abrams <mabrams>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Juno	CC:	yeylon
Target Milestone:	---
Target Release:	Juno
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-puppet-modules-2014.2.12-4.fc22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1187706 (view as bug list)		Environment:
Last Closed:	2016-03-30 23:05:26 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:
Bug Depends On:
Bug Blocks:	1082728

Description Rich Megginson 2015-01-26 17:10:34 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Rich Megginson 2015-01-26 17:13:36 UTC

When using Keystone with an LDAP identity backend, the default_project_id is not stored in the entry e.g. openstack user list and user show will display an empty project.  openstack user role list --project must be used to test if the user is a member of the tenant/project.  The puppet-keystone module needs to be aware of how to handle tenant/project when there is an LDAP backend.

Note that this particular change also depends on the switch of puppet-keystone to use the openstack client instead of the keystone client.

Comment 2 Rich Megginson 2015-02-20 18:29:10 UTC

upstream has merged the fix.  Can we get this into rdo opm?  Should this bug be moved to POST now?