Public bug reported:
I have Mitaka implemented in a multihost platform. All the hypervisors have
minimal required disk. The VMs are stored on a seperate storage cinder host
with lvm backend. Whenever I launch an instance with Boot from image(Create a
new Volume), it is incorrectly adding up the new volume size into "Local Disk
Usage" or "local_gb_used". If the volume size is beyond the Local Storage
available, though the cinder lvm backend has enough storage, instance fails to
launch with error. But if the instance volume size is within "Local Disk", the
instance launch successfully and also the volume is created correctly in the
lvm cinder backend.
The issue here is that while launching the instance it considers the local disk
of the hypervisors and adds up to its local consumption.
nova hypervisor-stats
+----------------------+--------+
| Property | Value |
+----------------------+--------+
| count | 7 |
| current_workload | 0 |
| disk_available_least | 98 |
| free_disk_gb | 64 |
| free_ram_mb | 71369 |
| local_gb | 126 |
| local_gb_used | 274 |
| memory_mb | 112329 |
| memory_mb_used | 40960 |
| running_vms | 7 |
| vcpus | 56 |
| vcpus_used | 13 |
+----------------------+--------+
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1660655
Title:
Any instance that is boot from new volume adding up to local_gb_used
Status in OpenStack Compute (nova):
New
Bug description:
I have Mitaka implemented in a multihost platform. All the hypervisors have
minimal required disk. The VMs are stored on a seperate storage cinder host
with lvm backend. Whenever I launch an instance with Boot from image(Create a
new Volume), it is incorrectly adding up the new volume size into "Local Disk
Usage" or "local_gb_used". If the volume size is beyond the Local Storage
available, though the cinder lvm backend has enough storage, instance fails to
launch with error. But if the instance volume size is within "Local Disk", the
instance launch successfully and also the volume is created correctly in the
lvm cinder backend.
The issue here is that while launching the instance it considers the local
disk of the hypervisors and adds up to its local consumption.
nova hypervisor-stats
+----------------------+--------+
| Property | Value |
+----------------------+--------+
| count | 7 |
| current_workload | 0 |
| disk_available_least | 98 |
| free_disk_gb | 64 |
| free_ram_mb | 71369 |
| local_gb | 126 |
| local_gb_used | 274 |
| memory_mb | 112329 |
| memory_mb_used | 40960 |
| running_vms | 7 |
| vcpus | 56 |
| vcpus_used | 13 |
+----------------------+--------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1660655/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
