yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #23178
[Bug 1335999] Re: live migration choosing wrong host names
** Changed in: horizon
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1335999
Title:
live migration choosing wrong host names
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Horizon's admin interface recently gained a feature to trigger a live
migration from the UI. It requires a destination host to be specified
(which is wrong, as the destination host is optional in the API), and
it allows to preselect from a list of given names.
However, the list that is chosen is coming from os-hypervisor-list.
These host names might not match os-hosts, which is the one that the
nova scheduler expects.
Consequently if hypervisor names do not match the host names, the live
migration from the UI fails.
nova host-list is in my case:
+--------------------+-------------+----------+
| host_name | service | zone |
+--------------------+-------------+----------+
| d52-54-01-77-77-01 | scheduler | internal |
| d52-54-01-77-77-01 | consoleauth | internal |
| d52-54-02-77-77-02 | compute | nova |
| d52-54-01-77-77-01 | conductor | internal |
| d52-54-01-77-77-01 | cert | internal |
+--------------------+-------------+----------+
nova hypervisor-list is
nova hypervisor-list
+----+-------------------------------------+
| ID | Hypervisor hostname |
+----+-------------------------------------+
| 1 | d52-54-02-77-77-02.c6.cloud.suse.de |
+----+-------------------------------------+
calling a live-migration against the fqdn (like hypervisor-list returns) fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1335999/+subscriptions
References