local_gb_used wrong in compute_nodes table when using Dell Cinder backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
We have compute nodes with a very small amount of disk so we deploy our instances to Cinder volumes with a Dell backend.
The issue is that when creating instances with a Cinder volume it still gets counted towards the local storage used (local_gb_used in compute_nodes table of the nova database) which results in faulty information on what's actually stored on local disk.
Before:
nova hypervisor-stats
+------
| Property | Value |
+------
| local_gb | 425 |
| local_gb_used | 80 |
+------
cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
+------
nova list
+----+-
| ID | Name | Status | Task State | Power State | Networks |
+----+-
+----+-
After booting a new instance with 40 GB cinder volume.
nova hypervisor-stats
+------
| Property | Value |
+------
| local_gb | 425 |
| local_gb_used | 120 |
cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 15345aa2-
+------
nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 29cbe001-
+------
So the volume is counted as local storage which is wrong and prevents us from knowing if an instance has been
booted on local disk which we need to know since we don't have any local disk for usage.
Anybody got any clues?
Best regards
This bug is still active, I will be interesting to see if this has any negative impact ("such as failing when spawning instances") when the amount of used volume space exceeds the total amount of local disk space.