yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #03169
[Bug 1173376] Re: The hypervisor_hostname is not updated after live migration
** Changed in: nova/grizzly
Status: Fix Committed => Fix Released
--
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/1173376
Title:
The hypervisor_hostname is not updated after live migration
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Compute (nova) grizzly series:
Fix Released
Bug description:
After a live migration, we see the following instance data:
[root@z3-9-5-127-161 nova]# nova show aix_mig_109
+-------------------------------------+-------------------------------------------------------------------------+
| Property | Value |
+-------------------------------------+-------------------------------------------------------------------------+
| OS-EXT-STS:task_state | None |
| image | aix (cee63b35-a5e7-4f3c-ab04-5f52d288d743) |
| max_vcpus | 4.00 |
| OS-EXT-STS:vm_state | active |
| OS-EXT-SRV-ATTR:instance_name | nova-z3-9-5-127-161-0000002a |
| cpu_utilization | 0.2 |
| flavor | f59f51106a0738a6e827dc1abb74b8ca (93887940-b41c-4859-9000-1abbf6000352) |
| id | fe546877-872d-442f-be31-84a0d0c2b80e |
| security_groups | [{u'name': u'default'}] |
| user_id | 0ab4f16656dd418fac86f9893f65ec13 |
| pva network | 10.32.74.109 |
| OS-DCF:diskConfig | MANUAL |
| vcpus | 0.10 |
| accessIPv4 | |
| accessIPv6 | |
| progress | 0 |
| OS-EXT-STS:power_state | 1 |
| OS-EXT-AZ:availability_zone | nova |
| metadata | {} |
| status | ACTIVE |
| updated | 2013-04-25T21:42:40Z |
| hostId | f10a414b4a0b02c51051fea9f4c51697ade6b34a84248bd3ca535416 |
| OS-EXT-SRV-ATTR:host | pva138 |
| memory_mode | dedicated |
| key_name | None |
| vcpu_mode | shared |
| min_memory_mb | 512 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | pva137 |
| name | aix_mig_109 |
| created | 2013-04-25T21:22:12Z |
| tenant_id | f8fabb7a96d24e4e97d0a2926576a90a |
| min_vcpus | 0.10 |
| memory_mb | 512 |
| health_status | {u'health_value': u'OK'} |
| max_memory_mb | 4096 |
+-------------------------------------+-------------------------------------------------------------------------+
Note that host and hypervisor_hostname no longer match (and they
should in this case). It appears the hypervisor_hostname was not
updated after the live migration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1173376/+subscriptions