Comment 4 for bug 897326

 I guess the reason nova do not check if the tenant/project exist is because nova do not maintain tenant information by itself,.

nova-manage command will directly change nova database, so looks really difficult to add tenant/project check.

On the other side, actually, I think, for a nova client, no matter what role the user is, it can only show, update quota for its own tenant. So, the easiest way to fix this is to remove the input parameter in nova-client, make sure it will only operate on its own tenant.

Or, nova-api should check with keystone if the tenant exist before excute quota related command.

Is this correct?