Bug 1041897

Summary:	[RFE][keystone]: Do not check for user when creating assignment
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:	Udi Kalifon <ukalifon>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aberezin, ayoung, breeler, markmc, nkinder, ukalifon, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/no-check-id
Whiteboard:	upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_new
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-26 15:26:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 19:57:30 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/no-check-id.

Description:

Creating an assignment may happen in the absence of User data.  For Federation, a user listing may not even be possible.  Even in LDAP and SQL cases, an admin may need to create role assignments prior to a valid user object being available.  Same is tru for groups. These checks are unnecessary, and can and should be removed.

Specification URL (additional information):

None

Comment 2 Udi Kalifon 2014-03-31 06:41:41 UTC

This will not be fixed and the RFE is invalid. See my upstream bug on this which was tagged as "invalid":
https://bugs.launchpad.net/keystone/+bug/1298478

Should we close this bz?

Comment 3 Adam Young 2014-04-02 13:23:32 UTC

Yes, lets close it.  I'll mention to upstream we should remove this line from the release notes, as the BP is not fully implemented.