VMwareVCDriver and VMwareESXDriver doesn't update memory, disk and cpu usage to account for externally allocated VMs
Bug #1240200 reported by
Maithem
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
The ESX driver doesn't account for resources that have been allocated without nova-compute. When nova-compute first launches, it polls the esx hypervisor for available resources and initializes the disk/memory/vcpu usage metrics with incorrect values (assumes all resources are available). Which can result in over allocation errors when provisioning new virtual machines.
How to reproduce:
1. Create a virtual machine on the ESX hypervisor(using vsphere client)
2. Launch Nova
3. Check the "Hypervisor Summary" page on the dashboard
4. Notice that the disk/memory/vcpu usage doesn't reflect the virtual machine's(from step 1) allocated resources
summary: |
- ESX drive report incorrect metrics for memory, disk and cpu usage + VMware ESX driver reports incorrect metrics for memory, disk and cpu + usage |
description: | updated |
Changed in nova: | |
status: | New → Confirmed |
summary: |
- VMware ESX driver reports incorrect metrics for memory, disk and cpu - usage + VMware VCdriver doesn't update memory, disk and cpu usage to account + for externally allocated VMs |
summary: |
- VMware VCdriver doesn't update memory, disk and cpu usage to account - for externally allocated VMs + VMwareVCDriver and VMwareESXDriver doesn't update memory, disk and cpu + usage to account for externally allocated VMs |
Changed in nova: | |
assignee: | Maithem (maithem) → nobody |
To post a comment you must log in.
Hi
Can you check for the following lines in nova-compute log and post them here :-
>Auditing locally available compute resources
>Hypervisor: free ram (MB): XYZ
>Hypervisor: free disk (GB): XY
>Hypervisor: free VCPUs: X
This is the hypervisor's view of resource usage that is reported by the drivers to the compute manager. The usage stats here would account for the existing instances on the ESX host/ VC Cluster. The usage stats on the Hypervisor page is the usage based on instances.