yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #17657
[Bug 1285259] Re: After evacuate origin host still report a runing vm
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => juno-2
--
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/1285259
Title:
After evacuate origin host still report a runing vm
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
After evacuate a host with one instance to a target host it still
report there is an instance in that hypervisor
Pre evacuate report:
$ nova hypervisor-stats
+----------------------+-------+
| Property | Value |
+----------------------+-------+
| count | 2 |
| current_workload | 0 |
| disk_available_least | 22 |
| free_disk_gb | 50 |
| free_ram_mb | 3860 |
| local_gb | 50 |
| local_gb_used | 0 |
| memory_mb | 4948 |
| memory_mb_used | 1088 |
| running_vms | 1 |
| vcpus | 3 |
| vcpus_used | 1 |
+----------------------+-------+
$ nova hypervisor-list
+----+---------------------+
| ID | Hypervisor hostname |
+----+---------------------+
| 1 | jmolle-Controller |
| 2 | jmolle-Node1 |
+----+---------------------+
$ nova hypervisor-show jmolle-Controller
+---------------------------+-------------------------------------------------------+
| Property | Value |
+---------------------------+-------------------------------------------------------+
| cpu_info_arch | x86_64 |
| cpu_info_features | ["rdtscp", "hypervisor", "x2apic", "ss", "ds", "vme"] |
| cpu_info_model | Westmere |
| cpu_info_topology_cores | 1 |
| cpu_info_topology_sockets | 2 |
| cpu_info_topology_threads | 1 |
| cpu_info_vendor | Intel |
| current_workload | 0 |
| disk_available_least | 10 |
| free_disk_gb | 25 |
| free_ram_mb | 3378 |
| host_ip | 192.168.41.101 |
| hypervisor_hostname | jmolle-Controller |
| hypervisor_type | QEMU |
| hypervisor_version | 1000000 |
| id | 1 |
| local_gb | 25 |
| local_gb_used | 0 |
| memory_mb | 3954 |
| memory_mb_used | 576 |
| running_vms | 1 |
| service_host | jmolle-Controller |
| service_id | 4 |
| vcpus | 2 |
| vcpus_used | 1 |
+---------------------------+-------------------------------------------------------+
$ nova hypervisor-servers jmolle-Controller
+--------------------------------------+-------------------+---------------+---------------------+
| ID | Name | Hypervisor ID | Hypervisor Hostname |
+--------------------------------------+-------------------+---------------+---------------------+
| a3c291e5-05b0-43fc-b16b-121bf36f30c0 | instance-00000001 | 1 | jmolle-Controller |
+--------------------------------------+-------------------+---------------+---------------------+
But after evacuate the instanse we get:
$ nova hypervisor-stats
+----------------------+-------+
| Property | Value |
+----------------------+-------+
| count | 2 |
| current_workload | 1 |
| disk_available_least | 22 |
| free_disk_gb | 50 |
| free_ram_mb | 3796 |
| local_gb | 50 |
| local_gb_used | 0 |
| memory_mb | 4948 |
| memory_mb_used | 1152 |
| running_vms | 2 |
| vcpus | 3 |
| vcpus_used | 2 |
+----------------------+-------+
here we see that now there are 2 running instances instead of one
and if we use show command we get:
$ nova hypervisor-show jmolle-Controller
+---------------------------+-------------------------------------------------------+
| Property | Value |
+---------------------------+-------------------------------------------------------+
| cpu_info_arch | x86_64 |
| cpu_info_features | ["rdtscp", "hypervisor", "x2apic", "ss", "ds", "vme"] |
| cpu_info_model | Westmere |
| cpu_info_topology_cores | 1 |
| cpu_info_topology_sockets | 2 |
| cpu_info_topology_threads | 1 |
| cpu_info_vendor | Intel |
| current_workload | 0 |
| disk_available_least | 10 |
| free_disk_gb | 25 |
| free_ram_mb | 3378 |
| host_ip | 192.168.41.101 |
| hypervisor_hostname | jmolle-Controller |
| hypervisor_type | QEMU |
| hypervisor_version | 1000000 |
| id | 1 |
| local_gb | 25 |
| local_gb_used | 0 |
| memory_mb | 3954 |
| memory_mb_used | 576 |
| running_vms | 1 |
| service_host | jmolle-Controller |
| service_id | 4 |
| vcpus | 2 |
| vcpus_used | 1 |
+---------------------------+-------------------------------------------------------+
we also see 1 running instance
but if we list servers we get 0
$ nova hypervisor-servers jmolle-Controller
+----+------+---------------+---------------------+
| ID | Name | Hypervisor ID | Hypervisor Hostname |
+----+------+---------------+---------------------+
+----+------+---------------+---------------------+
and the instance was evacuate to the other host correctly
$ nova hypervisor-servers jmolle-Node1
+--------------------------------------+-------------------+---------------+---------------------+
| ID | Name | Hypervisor ID | Hypervisor Hostname |
+--------------------------------------+-------------------+---------------+---------------------+
| a3c291e5-05b0-43fc-b16b-121bf36f30c0 | instance-00000001 | 2 | jmolle-Node1 |
+--------------------------------------+-------------------+---------------+---------------------+
I think this is a nova bug due to the inconcistency of hypervisor-show
and hypervisor-servers nova commands
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1285259/+subscriptions
References
