Ask Your Question
0

Error in Migrating VM's from one host machine to another. i am using Openstack Juno on CentOs 7.

asked 2015-03-13 06:09:08 -0500

HK gravatar image

When Trying to migrate VM's from one host to another host. I get the following error:

Error: Failed to launch instance "XYZ": Please try again later [Error: Unexpected error while running command. Command: ssh 172.16.32.* mkdir -p /var/lib/nova/instances/520c189a-d14d-4e31-8364-2f88648d7089 Exit code: 255 Stdout: u'' Stderr: u'Host key verification failed.\r\n'].

I am using openstack juno and CentOs 7 and have configured Controller on one host machine and Compute on another host machine.

Please suggest why this error is coming and how can it be resolved. Please elaborate as i m relatively new to openstack.

edit retag flag offensive close merge delete

Comments

Someone please help !! I am migrating instances using OpenStack Dashboard.

HK gravatar imageHK ( 2015-03-13 06:10:55 -0500 )edit
1

Can the user nova ssh between controllers and compute nodes without being asked for a password?

lnxslck gravatar imagelnxslck ( 2015-03-13 06:16:47 -0500 )edit
1

Also check the admin_password in the nova files configuration. They must be the same in all controllers and computes.

lnxslck gravatar imagelnxslck ( 2015-03-13 06:19:05 -0500 )edit

Inxslck.. can u please elaborate on your answer. I am quite new to this and really not getting how to proceed with fixing of the above error. On the broader picture ... Can you figure out what this error is due to ? Is it due to some key-pair issues ?

HK gravatar imageHK ( 2015-03-13 13:15:41 -0500 )edit

How to switch to nova user to test ssh between compte nodes ?

HK gravatar imageHK ( 2015-03-22 07:48:26 -0500 )edit

3 answers

Sort by » oldest newest most voted
1

answered 2015-03-13 13:59:27 -0500

Access the destination host & confirm if the instance directory exists, it should be:

/var/lib/nova/instances/520c189a-d14d-4e31-8364-2f88648d7089

if the directory doesn't exist create it (mkdir) and update the ownership to nova (chown -R nova:nova) then start the vm again and it should work.

edit flag offensive delete link more

Comments

This changes the error but it does not resolve the problem of migration. Also will i need to manually add this directory for every instance that i create and wish to migrate. It isn't working. Please suggest some other solution.

HK gravatar imageHK ( 2015-03-16 11:05:31 -0500 )edit

you shouldn't have to do this manually every time. What kind of file system are you using and what do you have in the nova.conf file under live_migration_flag=

raul.flores gravatar imageraul.flores ( 2015-03-24 10:59:02 -0500 )edit

In nova.conf file, live_migration_flag is commented

#live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_LIVE, VIR_MIGRATE_TUNNELLED

what to do next?

HK gravatar imageHK ( 2015-03-25 01:06:53 -0500 )edit
1

Ok, that is the default. Have you reviewed the Configure Migrations document to ensure everything is correctly configured?

http://docs.openstack.org/admin-guide...

What error are you seeing now?

raul.flores gravatar imageraul.flores ( 2015-03-25 09:58:22 -0500 )edit
1

answered 2015-09-15 03:30:17 -0500

fifieldt gravatar image

Hi,

It sounds like you might need to perform some additional steps to configure your cloud for live migrations. Particularly, you need to set up SSH so your hypervisor hosts can log into each other (if you google "Host Key Verification Failed" you will find some techniques to deal with this, such as distributing a known_hosts file).

Further information about migrations can be found in the Admin Guide at http://docs.openstack.org/admin-guide...

edit flag offensive delete link more
0

answered 2015-07-10 00:18:09 -0500

liyahua gravatar image

updated 2015-07-10 00:38:27 -0500

I have also met this problem , from my point of view ,there is something wrong with the authentication. my error is like this : 错误: Unexpected error while running command. Command: ssh 10.0.0.21 mkdir -p /var/lib/nova/instances/f5340ef9-2a8a-48ff-a55c-a6716abbb67f Exit code: 255 Stdout: u'' Stderr: u'Host key verification failed.\r\n'].

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-03-13 06:09:08 -0500

Seen: 4,309 times

Last updated: Sep 15 '15