Open Stack

> Yup, the UX is horrible for this one. can you expand on the error
masking point?

That was an error I saw in Essex where one type of quota exception would
be thrown when another type was exceeded. I'll check in our Havana setup
and see if it is still a problem. I'll file a separate report if it is.

> I am not sure how you want to change things. For this to be confirmed
I would like a more explicit explanation of what the issue is and what
the desired outcome should be.

I think the simple fix is to have the nova api check against Keystone to
validate the UUID before sending a response to the client. I'll update
the bug description to suggest this solution.

-- 
You received this bug notification because you are a member of OpenStack
Security Group, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1118066

Title:
  Possible to get and update quotas for nonexistant tenant

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  GET /v2/:tenant/os-quota-sets/:this_tenant_does_not_exist
  returns 200 with the default quotas.

  Moreover
  POST /v2/:tenant/os-quota-sets/:this_tenant_does_not_exist
  with updated quotas succeeds and that metadata is saved!

  I'm not sure if this is a bug or not. I cannot find any documentation
  on this interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1118066/+subscriptions