openstack/nova
Code Issues Proposed changes

doc: Add solution to live migration ssh issues

Browse Source 
This took me a good hour to suss and while there were a couple of Google
hits for it, the top suggestion was to use TCP (rather than SSH) and
disable all security, which is rarely good advice.

Paste an sample error and link to the doc where you can find advice of
resolving the issue.

Change-Id: I3805361834f7d954ae6759a22f61f02db139bcc5
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This commit is contained in:
Stephen Finucane 2018-12-21 14:49:36 +00:00
parent 4da306f640
commit 76aea693dc
1 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
doc/source/admin/support-compute.rst
View File

@ -112,6 +112,35 @@ Also, check your HTTP proxy settings to see whether they cause problems with
``novarc`` creation.
Live migration permission issues
--------------------------------
Problem
~~~~~~~
When live migrating an instance, you may see errors like the below:
.. code-block:: shell
libvirtError: operation failed: Failed to connect to remote libvirt URI
qemu+ssh://stack@cld6b16/system: Cannot recv data: Host key verification
failed.: Connection reset by peer
Solution
~~~~~~~~
Ensure you have completed all the steps outlined in
:doc:`/admin/ssh-configuration`. In particular, it's important to note
that the ``libvirt`` process runs as ``root`` even though it may be connecting
to a different user (``stack`` in the above example). You can ensure everything
is correctly configured by attempting to connect to the remote host via the
``root`` user. Using the above example once again:
.. code-block:: shell
$ su - -c 'ssh stack@cld6b16'
Instance errors
---------------