"Quota exceeded" message is confusing for "resize"

Bug #1951617 reported by Belmiro Moreira
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Low
Belmiro Moreira

Bug Description

"Quota exceeded" message is confusing for "resize"

When trying to create an instance and there is no quota available, the user gets an error message.
example:
"Quota exceeded for cores: Requested 1, but already used 100 of 100 cores (HTTP 403)"

The user can see that the project is already using 100 vCPUs out of 100 vCPUs available (vCPU quota) in the project.

However, if he tries to resize an instance we can get a similar error message:
"Quota exceeded for cores: Requested 2, but already used 42 of 100 cores (HTTP 403)"

So, this has a completely different meaning!
It means that the user (of the instance that he's trying to resize) is using 42 vCPUs in the project out of 100 cores allowed by the quota.

This is hard to understand for a end user.
When naively reading this message looks like the project still has plenty of resources for the resize.

I believe this comes from the time when Nova allowed quotas per user.
In my opinion this distinction shouldn't be done anymore. As mentioned we don't do it when creating a new instance.

+++

This was tested with the master branch (19/11/2021)

Tags: quotas
Changed in nova:
assignee: nobody → Belmiro Moreira (moreira-belmiro-email-lists)
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
tags: added: quotas
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/nova/+/820898

Changed in nova:
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.