Incorrect volume usage notifications on migration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Gorka Eguileor |
Bug Description
Volume usage notifications in Cinder during Cinder volume migrations are incorrect.
Part of a volume migration is creating a new volume on the destination backend and during this process Cinder will issue volume usage notifications "create.start" and "create.end" even though this is not a user volume creation and is inconsistent with other temporary volume and snapshot creation cases.
Also one of the latest steps during the volume creation is to delete one of the 2 volumes (the source or the destination) and in that case Cinder will only issue a "delete.end" notification without its corresponding "delete.start".
Since temporary volumes (for backups or migrations) are not counted towards quota usage they should also not issue volume usage notifications.
Changed in cinder: | |
importance: | Undecided → Medium |
tags: | added: migration notifications quota |
Fix proposed to branch: master /review. opendev. org/c/openstack /cinder/ +/786383
Review: https:/