Quota errors occur when Cinder creates a temporary volume to handle operations such as backing up another in-use volume. +++ This bug was initially created as a clone of Bug #1584499 +++
Verified on: openstack-cinder-12.0.3-2.el7ost.noarch Initial quota (no volume) of a demo project/user cinder quota-usage d44764a39871480aa6c14763ef8126c4 +----------------------+--------+----------+-------+-----------+ | Type | In_use | Reserved | Limit | Allocated | +----------------------+--------+----------+-------+-----------+ | backup_gigabytes | 0 | 0 | 1000 | | | backups | 0 | 0 | 10 | | | gigabytes | 0 | 0 | 1000 | | | groups | 0 | 0 | 10 | | | per_volume_gigabytes | 0 | 0 | -1 | | | snapshots | 0 | 0 | 10 | | | volumes | 0 | 0 | 10 | | +----------------------+--------+----------+-------+-----------+ All operations below were done on demo project/user cinder create 2 id | d59b523b-268b-43d1-91bc-04b1cc295bcf cinder quota-usage d44764a39871480aa6c14763ef8126c4 +----------------------+--------+----------+-------+-----------+ | Type | In_use | Reserved | Limit | Allocated | +----------------------+--------+----------+-------+-----------+ | backup_gigabytes | 0 | 0 | 1000 | | | backups | 0 | 0 | 10 | | | gigabytes | 2 | 0 | 1000 | | | groups | 0 | 0 | 10 | | | per_volume_gigabytes | 0 | 0 | -1 | | | snapshots | 0 | 0 | 10 | | | volumes | 1 | 0 | 10 | | +----------------------+--------+----------+-------+-----------+ Boot an instance attach volume nova volume-attach ceddad6b-6bd5-45b5-9094-9ae52a49ef07 d59b523b-268b-43d1-91bc-04b1cc295bcf auto cinder backup-create d59b523b-268b-43d1-91bc-04b1cc295bcf --force During backup Every 5.0s: cinder quota-usage d44764a39871480aa6c14763ef8126c4 Mon Aug 6 23:43:53 2018 +----------------------+--------+----------+-------+-----------+ | Type | In_use | Reserved | Limit | Allocated | +----------------------+--------+----------+-------+-----------+ | backup_gigabytes | 2 | 0 | 1000 | | | backups | 1 | 0 | 10 | | | gigabytes | 2 | 0 | 1000 | | | groups | 0 | 0 | 10 | | | per_volume_gigabytes | 0 | 0 | -1 | | | snapshots | 0 | 0 | 10 | | | volumes | 1 | 0 | 10 | | +----------------------+--------+----------+-------+-----------+ Post backup cinder quota-usage d44764a39871480aa6c14763ef8126c4 +----------------------+--------+----------+-------+-----------+ | Type | In_use | Reserved | Limit | Allocated | +----------------------+--------+----------+-------+-----------+ | backup_gigabytes | 2 | 0 | 1000 | | | backups | 1 | 0 | 10 | | | gigabytes | 2 | 0 | 1000 | | | groups | 0 | 0 | 10 | | | per_volume_gigabytes | 0 | 0 | -1 | | | snapshots | 0 | 0 | 10 | | | volumes | 1 | 0 | 10 | | +----------------------+--------+----------+-------+-----------+ As expected on a none admin project/user (demo) Cinder's quota remains on 2G as expected before during and after a forced backup of an in use volume.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2594