← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1716706] [NEW] Should count instances in build requests when check quotas

 

Public bug reported:

In https://blueprints.launchpad.net/nova/+spec/cells-count-resources-to-check-quota-in-api we
changed to use new quota check workflows which counts all consumed resources across cells and
comparing with the limits.

But the resources in build_requests was not counted and this might
lead to creating 20 instances in concurrent requests, i'll probably get 10 in ERROR state rather
than 10 plus 10 failed requests with 409s. Which might be a big change to users.

We should also count instance records from build requests as consumed resources in order to
avoid allowing creation requests pass API layer checks and stopped in conductor layer check,
which lead instances to ERROR state.

** Affects: nova
     Importance: High
     Assignee: Zhenyu Zheng (zhengzhenyu)
         Status: Triaged


** Tags: quotas

** Changed in: nova
     Assignee: (unassigned) => Zhenyu Zheng (zhengzhenyu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1716706

Title:
  Should count instances in build requests when check quotas

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  In https://blueprints.launchpad.net/nova/+spec/cells-count-resources-to-check-quota-in-api we
  changed to use new quota check workflows which counts all consumed resources across cells and
  comparing with the limits.

  But the resources in build_requests was not counted and this might
  lead to creating 20 instances in concurrent requests, i'll probably get 10 in ERROR state rather
  than 10 plus 10 failed requests with 409s. Which might be a big change to users.

  We should also count instance records from build requests as consumed resources in order to
  avoid allowing creation requests pass API layer checks and stopped in conductor layer check,
  which lead instances to ERROR state.

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