Bug 1033940 - openstack-nova: instance migration fail
Summary: openstack-nova: instance migration fail
Keywords:
Status: CLOSED DUPLICATE of bug 1028186
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 4.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: 4.0
Assignee: Xavier Queralt
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-24 14:41 UTC by Yogev Rabl
Modified: 2019-09-09 17:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-25 07:50:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
nova logs (2.36 MB, text/x-log)
2013-11-24 14:41 UTC, Yogev Rabl
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1254450 0 None None None Never

Description Yogev Rabl 2013-11-24 14:41:35 UTC
Created attachment 828342 [details]
nova logs

Description of problem:
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. 

Version-Release number of selected component (if applicable):
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.

Additional info:

Comment 3 Xavier Queralt 2013-11-25 07:50:06 UTC
In the log I can see the message "Host key verification failed".

Before using resize/migrate without shared storage the hosts must be configured to allow passwordless access for user nova so the image can be copied from one host to the other using ssh. You can find the exact configuration steps in: http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL#Migrate_and_Resize

*** This bug has been marked as a duplicate of bug 1028186 ***


Note You need to log in before you can comment on or make changes to this bug.