Comment 7 for bug 1927186

I'm wondering about real impact of this miscalculation of allocated_capacity_gb. By the look of it, the scheduler will incorrectly schedule volumes to less busy cinder-volume service. However the free_capacity_gb will still be reported correctly. So there is no risk of overcommit the backend. Therefore for setup with one backend managed by multiple HA cinder-volume service that is not a huge issue?

Furthermore quota management is also probably not impacted here as well.