Public bug reported:
version: commit ce5a2fb419f999bec0fb2c67413387c8b67a691a
1. create a boot-from-volume instance prior to deploying commit
5bd222e8d854ca7f03ee6936454ee57e0d6e1a78
2. upgrade nova to commit 5bd222e8d854ca7f03ee6936454ee57e0d6e1a78
3. live-migrate instance
4. observe live-migrate action fail
based on my analysis of logs and code:
1. destination uses new-style SR naming convention in sr_uuid_map.
2. source tries to use new-style SR naming convention in talking to XenAPI (in
nova.virt.xenapi.vmops.py:VMOps.live_migrate() -> _call_live_migrate_command())
3. xenapi throws XenAPI.Failure exception because it "Got exception
UUID_INVALID" because it only knows the SR by the old-style naming convention
example destination nova-compute, source nova-compute, and xenapi logs
from a live-migrate request to follow.
** Affects: nova
Importance: Undecided
Status: New
** Tags: live-migrate nova xenapi
** Attachment added: "destination nova-compute, source nova-compute, and xenapi
logs from a live-migrate request"
https://bugs.launchpad.net/bugs/1566622/+attachment/4625560/+files/live-migrate_fails_with_old_and_new-style_sr_naming_convention.log
--
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/1566622
Title:
live migration fails with xenapi virt driver and SRs with old-style
naming convention
Status in OpenStack Compute (nova):
New
Bug description:
version: commit ce5a2fb419f999bec0fb2c67413387c8b67a691a
1. create a boot-from-volume instance prior to deploying commit
5bd222e8d854ca7f03ee6936454ee57e0d6e1a78
2. upgrade nova to commit 5bd222e8d854ca7f03ee6936454ee57e0d6e1a78
3. live-migrate instance
4. observe live-migrate action fail
based on my analysis of logs and code:
1. destination uses new-style SR naming convention in sr_uuid_map.
2. source tries to use new-style SR naming convention in talking to XenAPI
(in nova.virt.xenapi.vmops.py:VMOps.live_migrate() ->
_call_live_migrate_command())
3. xenapi throws XenAPI.Failure exception because it "Got exception
UUID_INVALID" because it only knows the SR by the old-style naming convention
example destination nova-compute, source nova-compute, and xenapi logs
from a live-migrate request to follow.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1566622/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
