Wrong handling of domain_id passed as None

Bug #1490764 reported by Henrique Truta
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Invalid
Undecided
Unassigned

Bug Description

Keystone does not handle the domain_id passed as none in controller layer, as in:

https://github.com/openstack/keystone/blob/master/keystone/common/controller.py#L743

lei zhang (zhang-lei)
Changed in keystone:
status: New → Confirmed
assignee: nobody → lei zhang (zhang-lei)
lei zhang (zhang-lei)
Changed in keystone:
status: Confirmed → New
assignee: lei zhang (zhang-lei) → nobody
Revision history for this message
lei zhang (zhang-lei) wrote :

domain_id is not a variable, it can't be None

as in: https://github.com/openstack/keystone/blob/master/keystone/common/controller.py#L743

This step is just to judge whether ref['domain_id'] is already exists

Changed in keystone:
status: New → Invalid
Revision history for this message
David Stanek (dstanek) wrote :

@Lei, I think the key can be None from the V2 API. I think most cases in V3 make it a string or it can't be provided at all.

@Henrique, How is the handing wrong?

Changed in keystone:
status: Invalid → New
status: New → Incomplete
Revision history for this message
Henrique Truta (henriquetruta) wrote :

@David, we are not handling domain_id None... In project creation, it should look at the token to get the domain_id in case None or nothing was provided. See Henry's comment here: https://review.openstack.org/#/c/213448/6/keystone/common/controller.py

@Lei see the link above

Revision history for this message
Henrique Truta (henriquetruta) wrote :

Marking as invalid, as this is a new behaviour and should be fixed in this same patch.

Changed in keystone:
status: Incomplete → Opinion
status: Opinion → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.