72da8249d9
When the volume service starts up, it goes through all volumes for a host in the db and adds up the volume size as a mechanism to account for that allocate space against the backend. The problem was that the volume manager was only counting volumes with a state of 'in-use' or 'available'. If a volume has a host set on it, then we account for it's allocated space. This patch adds other volume states to use to account for allocated space at volume service startup. Closes-Bug: 1910767 Change-Id: I90d5dfbe62e630dc8042e725d411cadc2762db56
8 lines
295 B
YAML
8 lines
295 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #1910767 <https://bugs.launchpad.net/cinder/+bug/1910767>`_: Fixed
|
|
the calculation of the allocated capacity for the volume manager.
|
|
The fix takes into account all volumes that have a host setting, not just
|
|
volumes with a status of 'in-use' or 'available'.
|