nova quota-show didn't report error when provide a non-existing tenant-id

[xiaohanyu]

Seems "nova quota-show --tenant" doesn't check whether or not the "tenant id" is existing.

I think in normal ways, this should report a error if you provide a illegal tenant id.

Steps to reproduce:

Just type "nova quota-show --tenant non-existing-tenant-id", and nova will show you the default quota settings for any tenant.

[Chris Buccella (chris-buccella)]

Hmm.... I get an HTTP 403 when I try this.

Perhaps something specific to your setup is allowing this to occur.

[melanie witt (melwitt)]

I also get "ERROR: Access was denied to this resource. (HTTP 403)" when I try to reproduce the issue as non-admin.

As admin, I do see quota settings even with a non-existent tenant id.

[Abhishek Chanda (abhishek-i)]

As an admin user, when I run the curl command, I see quota settings:

1. As an admin user, do nova --debug quota-show --tenant blahblah
2. Get the curl command
3. Run it by hand

This makes this a bug in nova and not the client

[Jian Wen (wenjianhn)]

I filed bug 1200585 which is also related to non-existing tenant-id.

I think we need to start a discussion on mailing list.

[Thang Pham (thang-pham)]

There is a blueprint for this already and pending approval: https://blueprints.launchpad.net/openstack/?searchtext=validate-tenant-user-with-keystone. Marking this nova bug as a duplicate of bug #1313935.