yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53299
[Bug 1347039] Re: VMWare: available disk spaces(hypervisor-list) only based on a single datastore instead of all available datastores from cluster
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: Medium => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
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/1347039
Title:
VMWare: available disk spaces(hypervisor-list) only based on a single
datastore instead of all available datastores from cluster
Status in OpenStack Compute (nova):
Expired
Bug description:
Currently the with vmware backend nova hypervisor-list.
The local_gb, free_disk_gb, local_gb_used are not displaying correct values if the compute node(cluster) have more than 1 datastores. Currently the code only report the resource update picking up the first datastore which is incorrect.
The real situation is for example, 20 datastores availabel for the
compute cluster node, but it only calculate the 1 for resource report.
Which will cause easily deployment failure saying no freespace, in
fact there are enough disk for vm deployments.
[root@RegionServer1 nova]# nova hypervisor-show 1 +---------------------------+----
| Property | Value +---------------------------+-----
| cpu_info_model | ["Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU
X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz", "Intel(R) Xeon(R) CPU X5675 @ 3.07GHz"] | | cpu_info_topology_cores | 156
| cpu_info_topology_threads | 312
| cpu_info_vendor "IBM"]
| current_workload | 0
| disk_available_least | -
| free_disk_gb | -2682
| free_ram_mb | 1545886
| host_ip | 172.18.152.120
| hypervisor_hostname | domain-c661(BC1-Cluster)
| hypervisor_type | VMware vCenter Server
| hypervisor_version | 5001000
| id | 1
| local_gb | 1799
| local_gb_used | 4481
| memory_mb | 1833630
| memory_mb_used | 287744
| running_vms | 281
| service_host | RegionServer1
| service_id | 6
| vcpus | 312
| vcpus_used | 281
+---------------------------+-------------
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1347039/+subscriptions
References