Automatic quota refresh counting twice migrating volumes

Bug #1917450 reported by Gorka Eguileor on 2021-03-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
High
Gorka Eguileor

Bug Description

When using the automatic quota refresh via `until_refresh` and `max_age` configuration options the calculated quota usage by the refresh will not be correct if there are volumes that are migrating, since source and destination volumes are counted in the refresh.

Normal quota usage calculation does not work like this, it only counts it once, and so should the automatic quota calculation.

Gorka Eguileor (gorka) on 2021-03-02
tags: added: quotas
Changed in cinder:
status: New → In Progress
importance: Undecided → High

This issue was fixed in the openstack/cinder 18.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers