yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #50260
[Bug 1576048] Re: "live_migration" call in Liberty doesn't have backwards compatibility with Kilo
Reviewed: https://review.openstack.org/310691
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=34b8336a41e2896f0639c402f64a05247f475fea
Submitter: Jenkins
Branch: master
commit 34b8336a41e2896f0639c402f64a05247f475fea
Author: Wenzhi Yu <wenzhi_yu@xxxxxxx>
Date: Thu Apr 28 16:06:57 2016 +0800
Make compute rpcapi 'live_migration' backward compatible
This commit[1] added compute rpcapi version 4.2 which introduced a new
argument 'migration' when calling 'live_migration' method, but the code
did not ensure the backward compatibility with older version compute
node.
When calling 'live_migration' method with 'migration' argument on older
version(like Kilo) of nova compute node, a "TypeError: live_migration()
got an unexpected keyword argument 'migration'" will be threw up.
[1]https://github.com/openstack/nova/commit/2f4e64a7cf81de4a22fe2fc4210b1f795b1a3db4
Change-Id: Ie5c498d34e7c4c6573d611abd592c25f1bcb4f44
Closes-Bug: #1576048
** Changed in: nova
Status: In Progress => 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/1576048
Title:
"live_migration" call in Liberty doesn't have backwards compatibility
with Kilo
Status in OpenStack Compute (nova):
Fix Released
Bug description:
"live_migration" call in Liberty doesn't have backwards compatibility
with Kilo.
Liberty control plane and Kilo compute nodes.
Doing live-migration and getting error below on compute node
TypeError: live_migration() got an unexpected keyword argument
'migration'
Workaround(On controller): http://paste.openstack.org/show/495612/
Environment
==========
Libvirt+KVM, Ceph for VMs
Liberty - Mirantis OpenStack 8.0 (2015.2)
Kilo - 2015.1.3 tag
Steps to reproduce
===============
1) Install Liberty control plane (api, conductor, schduler, etc.)
2) Install Kilo compute
3) Add to nova.conf on controller
[upgrade_levels]
compute=kilo
3) Try "nova live-migration VM"
Expected result
=============
Migration will succeed
Actual result
==========
Traceback on compute node
http://paste.openstack.org/show/495541/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1576048/+subscriptions
References