John.Garbutt at citrix
Jul 24, 2012, 8:51 AM
Post #2 of 2
(300 views)
Permalink
|
|
Re: live migration and unsupported rpc version
[In reply to]
|
|
Hi,
I recently pushed a changed to live-migration here:
https://review.openstack.org/#/c/8329/
Is it possible you have some parts of your system have not been updated? Maybe you have a new scheduler but an old compute node?
The default version is correctly 1.0. But the new live-migraiton changes mean that your compute/manager.py must be at version 1.2 in order to perform the migration.
I am fairly sure it worked when I tested it, but I may have missed something …
I hope that helps,
John
> From: Jānis Ģeņģeris [mailto:janis.gengeris [at] gmail]
> Sent: Monday, July 23, 2012 8:33 PM
> To: openstack-operators [at] lists
> Subject: [Openstack-operators] live migration and unsupported rpc version
>
> Hello,
>
> I'm trying to test out live migration but it fails with rcp version error, look below
>
> from nova-api.log
>
> 2012-07-23 20:07:49 TRACE
> nova.api.openstack.compute.contrib.admin_actions RemoteError: Remote
> error: RemoteError Remote error: UnsupportedRpcVersion Specified RPC
> version, 1.2, not supported by this endpoint.
>
> from nova-scheduler.log
> 2012-07-23 20:07:49 TRACE nova.openstack.common.rpc.amqp RemoteError:
> Remote error: UnsupportedRpcVersion Specified RPC version, 1.2, not
> supported by this endpoint.
>
> I'm using trunk latest trunk version (few days old).
>
> I'm initiating live migration with the following command:
> nova --debug live-migration e10f7e21-a5a5-496d-940c-6ee745e7b048
> compute2
>
> the debug output of the failure that I get in return:
> send: u'POST /v2/d5b04e149dfb4c849c34c03c840b0d6c/servers/e10f7e21-
> a5a5-496d-940c-6ee745e7b048/action HTTP/1.1\r\nHost:
> 192.168.1.1:8774\r\nContent-Length: 91\r\nx-auth-project-id:
> admin\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nx-auth-
> token: 417e6286fa4b4f9b9ec8fcc32bf52a4a\r\nuser-agent: python-
> novaclient\r\ncontent-type: application/json\r\n\r\n{"os-migrateLive":
> {"disk_over_commit": false, "block_migration": false, "host": "compute2"}}'
> reply: 'HTTP/1.1 400 Bad Request\r\n'
> header: Content-Length: 129
> header: Content-Type: application/json; charset=UTF-8
> header: X-Compute-Request-Id: req-927ed53d-40b9-4d7f-975a-2e1dfa637a34
> header: Date: Mon, 23 Jul 2012 19:19:47 GMT
>
> REQ: curl -i
> http://192.168.1.1:8774/v2/d5b04e149dfb4c849c34c03c840b0d6c/servers/e10f
> 7e21-a5a5-496d-940c-6ee745e7b048/action -X POST -H "X-Auth-Project-Id:
> admin" -H "User-Agent: python-novaclient" -H "Content-Type: application/json"
> -H "Accept: application/json" -H "X-Auth-Token:
> 417e6286fa4b4f9b9ec8fcc32bf52a4a"
>
> REQ BODY: {"os-migrateLive": {"disk_over_commit": false, "block_migration":
> false, "host": "compute2"}}
>
> RESP:{'date': 'Mon, 23 Jul 2012 19:19:47 GMT', 'status': '400', 'content-length':
> '129', 'content-type': 'application/json; charset=UTF-8', 'x-compute-request-id':
> 'req-927ed53d-40b9-4d7f-975a-2e1dfa637a34'} {"badRequest": {"message":
> "Live migration of instance e10f7e21-a5a5-496d-940c-6ee745e7b048 to host
> compute2 failed", "code": 400}}
>
>
> As I understand, then I need to set the RPC version somewhere, but where? I
> checked the config options, the only item that have something appropriate is
> the option for nova command with --os_compute_api_version, but the same
> errors remain when RPC API version is changed. After checking the source, I
> found that 'nova/compute/rpcapi.py', have default version set to '1.0'.
>
> Can you please shed some light about this issue?
> --
> --janis
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
|
