Quota usage should be updated if there's no valid host to run an instance

Bug #1308613 reported by Santiago Baldassin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Opinion
Undecided
Santiago Baldassin

Bug Description

When nova scheduler does not find a valid host to run an instance, the instance quota usage should be decremented.

Tags: compute quotas
Changed in nova:
assignee: nobody → Santiago Baldassin (santiago-b-baldassin)
Tracy Jones (tjones-i)
tags: added: compute
Revision history for this message
melanie witt (melwitt) wrote :

This needs a little more information. What do you see in this scenario i.e. is there an instance in ERROR state after you run the command? Unfortunately at present, instances in ERROR state do occupy quota which is only freed upon deleting them.

Changed in nova:
status: New → Incomplete
Revision history for this message
Santiago Baldassin (santiago-b-baldassin) wrote :

hi Melanie, yes, the instance is in Error state after the command. What I do not understand is why do instances in error state occupy quota?

Changed in nova:
status: Incomplete → Confirmed
tags: added: quota
Joe Gordon (jogo)
tags: added: quotas
removed: quota
Revision history for this message
Joe Gordon (jogo) wrote :

Instances in error state take up quota. This is for consistency since we generally count error state instances against the quota and having some count and others not count would be even more confusing.

Changed in nova:
status: Confirmed → Opinion
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.