Administrator can create resource, even if the tenant of resource is
different from the one of authentication. For example, administrator
can operate 'quantum net-create' command with different tenant
between the authentication tenant(--os-tenant-name) and --tenant-id.
In this case, quota cannot be restricted with the resource tenant,
because it is restricted with --os-tenant-name.
Reviewed: https:/ /review. openstack. org/29024 github. com/openstack/ quantum/ commit/ 84f65f387c873d7 d342a56f081f7bf 8025500bf9
Committed: http://
Submitter: Jenkins
Branch: master
commit 84f65f387c873d7 d342a56f081f7bf 8025500bf9
Author: fujioka yuuichi <email address hidden>
Date: Tue May 14 09:01:17 2013 +0900
fix reference to tenant id.
Administrator can create resource, even if the tenant of resource is --os-tenant- name) and --tenant-id.
different from the one of authentication. For example, administrator
can operate 'quantum net-create' command with different tenant
between the authentication tenant(
In this case, quota cannot be restricted with the resource tenant,
because it is restricted with --os-tenant-name.
This patch fixes this problem.
Fixes: bug #1179729
Change-Id: I8ce893bb583d52 f81c661082372d7 25bebf9c1be