nova migrate fails

[Yogev Rabl]

The nova migration fails while the instance:
- Has volume attached.
- The instance is active/ shutdown.
- The instance just been created with no volume attached.

The main nova compute node has ssh access to the secondary node, the Selinux and iptables are not a factor in the failure of the action.

the version is:
openstack-nova-compute-2013.2-5.el6ost.noarch
openstack-nova-scheduler-2013.2-5.el6ost.noarch
python-novaclient-2.15.0-1.el6ost.noarch
python-nova-2013.2-5.el6ost.noarch
openstack-nova-api-2013.2-5.el6ost.noarch
openstack-nova-conductor-2013.2-5.el6ost.noarch
openstack-nova-novncproxy-2013.2-5.el6ost.noarch
openstack-nova-cert-2013.2-5.el6ost.noarch
openstack-nova-common-2013.2-5.el6ost.noarch
openstack-nova-console-2013.2-5.el6ost.noarch

The OS is: Red Hat Enterprise Linux Server release 6.5

How reproducible:
everytime

Steps to Reproduce:
1. create an instance
2. migrate the instance (either when the instance is active or shutdown).
3.

Actual results:
the instance is in error state

Expected results:
the instance should move to the other nova-compute node and should be available.

The nova compute logs are attached.

[zhangjialong (zhangjl)]

Maybe you should create ssh key for user nova

[Vladik Romanovsky (vladik-romanovsky)]

I agree with zhangjl, It seems that there is something wrong with your ssh keys, as you can see from the logs:

Command: ssh 10.35.104.17 mkdir -p /var/lib/nova/instances/3b7ef5ae-94f4-44a8-a028-104e35cc9505
Exit code: 255
Stdout: ''
Stderr: 'Host key verification failed.\r\n'

Also, with this bug resolved https://bugs.launchpad.net/nova/+bug/1233184, the migrating instance will not be set to an ERROR state, on failed migration.