+++ This bug was initially created as a clone of Bug #2222825 +++

+++ This bug was initially created as a clone of Bug #2222824 +++

+++ This bug was initially created as a clone of Bug #2166486 +++

Copied from upstream bug [2]:

When nova is configured to count quota usage from placement [1], there are some behaviors that are different from the legacy quota resource counting.

With legacy quotas, all of an instance's resources remained consumed from a quota perspective while the instance was SHELVED_OFFLOADED. Because of this, there was no need to check quota when doing an unshelve and an unshelve request could not be blocked for quota related reasons. The quota usage remained the same whether the instance was SHELVED_OFFLOADED or not.

With counting quota usage from placement, cores and ram resource usage is counted from placement while instances are counted from the API database. And when an instance is SHELVED_OFFLOADED, it does not have any resource allocations in placement for cores and ram during that time. Because of this, it is possible to go over cores and ram quota after unshelving an instance as new resources will be allocated in placement for the unshelved instance.

The unshelve quota scenario is currently not being properly enforced because there are no quota checks in the scheduling code path, so when the unshelving instance goes through the scheduling process, it is not validated against quota. There needs to be a dedicated quota check for unshelve.

[1] https://docs.openstack.org/nova/latest/admin/quotas.html#quota-usage-from-placement

[2] https://bugs.launchpad.net/nova/+bug/2003991

— Additional comment from RHEL Program Management on 2023-02-01 23:49:29 UTC —

This item has been properly Triaged and planned for the release, and Target Release is now set to match the release flag. For details, see https://mojo.redhat.com/docs/DOC-1195410