Initially, the error was:

host key verification failed

So I created the host keys for nova user with the command: ssh-keygen -f
nova and then renamed them to id_rsa and id_rsa.pub and then put them to
~nova/.ssh/

Also, I copied the files /root/.ssh/known_hosts and
/root/.ssh/authorized_keys to ~nova/.ssh/ on both machines

Then I changed the file permissions to nova:nova

Then came the error:This account is currently not available.\n

So i edited the file /etc/passwd on both the machines and then changed the
line

nova:x:162:162:OpenStack Nova Daemons:/var/lib/nova:/sbin/nologin

to

nova:x:162:162:OpenStack Nova Daemons:/var/lib/nova:/bin/bash

Now migration works.. But his is a tedious task.


On Wed, May 29, 2013 at 5:45 PM, Mac Innes, Kiall <ki...@hp.com> wrote:

> On 29/05/13 13:11, Nehal J. Wani wrote:
> > 2013-05-29 17:39:04.795 5106 TRACE nova.openstack.common.rpc.amqp
> > ProcessExecutionError: Unexpected error while running command.
> > 2013-05-29 17:39:04.795 5106 TRACE nova.openstack.common.rpc.amqp
> > Command: ssh 10.3.3.58 mkdir -p
> > /var/lib/nova/instances/bc967b97-e103-4a13-abe4-ada8f98bdeb0
> > 2013-05-29 17:39:04.795 5106 TRACE nova.openstack.common.rpc.amqp Exit
> > code: 1
> > 2013-05-29 17:39:04.795 5106 TRACE nova.openstack.common.rpc.amqp
> > Stdout: 'This account is currently not available.\n'
> > 2013-05-29 17:39:04.795 5106 TRACE nova.openstack.common.rpc.amqp
> > Stderr: ''
> > 2013-05-29 17:39:04.795 5106 TRACE nova.openstack.common.rpc.amqp
> As the nova user, manually attempt that SSH command.. Then figure out
> why it can't SSH to the other node. It should work (or at least get
> further) once you do.
>
> Thanks,
> Kiall
>



-- 
Nehal J. Wani
UG2, BTech CS+MS(CL)
IIIT-Hyderabad
http://commanlinewani.blogspot.com
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to