hypervisor local_gb_used still reports usage even with volume-backed instances after fix for bug 1469179
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Zhenyu Zheng |
Bug Description
While testing the (partial) fix for bug 1469179:
https:/
Someone reported that nova hypervisor-
This is because of some code in the resource tracker that is not boot-from-volume aware when reporting disk usage, it just gets the root_gb off the flavor:
We have an instance uuid in scope for the callers of that code so we should be able to determine if it's a volume-backed instance and report 0 for root_gb if that's the case.
Long-term, once we drop the CachingScheduler and we can rely on allocations in placement, we should just change this code to report the disk usage based on the DISK_GB allocation against the given compute node provider for the given consumer (instance or migration record).
Changed in nova: | |
assignee: | nobody → Zhenyu Zheng (zhengzhenyu) |
Changed in nova: | |
assignee: | Zhenyu Zheng (zhengzhenyu) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Zhenyu Zheng (zhengzhenyu) |
This shows the bug: https:/ /review. openstack. org/#/c/ 583646/