Nova should use token's tenant, not user's one
Registered by
Alexej Ababilov
Currently, in nova queries, user default tenant is always used as nova's project in nova context. However, if token has a tenant, it should be used in place of user default one.
For example, we get a token qwerty for user joeuser (his default tenant is abc) and tenant xyz. Currently, nova will use context (joeuser, abc) for token qwerty. The correct behavior should be using (joeuser, xyz).
This patch fixed the issue:
https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Alexej Ababilov
- Definition:
- Obsolete
- Series goal:
- Accepted for diablo
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Jesse Andrews
Related branches
Related bugs
Sprints
Whiteboard
I thought Keystone default tenants no longer existed?
closing this as a blueprint because if this is still true then it is a bug
(?)
