[ovirt-users] Failed to Communicate with External Provider QEMU - related to RedHat Bug 1426573

[Tomáš Golembiovský]

On Tue, 17 Apr 2018 13:34:54 +0000
"Vrgotic, Marko" <M.Vrgotic at activevideo.com> wrote:

> If I try to use same proxy host, from command line, I am able to connect, no problems what so ever:
> 
> [root at aws-ovhv-07 vdsm]# virsh -c qemu+ssh://root@aws-ovhv-08.avinity.tv/system

You need to be running this as 'vdsm' user. See the "Additional info" in
the description of the bug you referenced. Or see the preparatory steps
described in [1]. The documentation is for Xen, but the steps are
analogous for KVM.

    Tomas

[1] https://www.ovirt.org/develop/release-management/features/virt/XenToOvirt/

> setlocale: No such file or directory
> The authenticity of host 'aws-ovhv-08.avinity.tv (172.16.81.57)' can't be established.
> ECDSA key fingerprint is SHA256:Ysbp/LvuOCIIvMbT931rwNN9HfBv1dtJpu0uQMi4lrk.
> ECDSA key fingerprint is MD5:14:c0:9c:bf:2b:65:ee:89:10:b8:21:54:57:72:9c:58.
> Are you sure you want to continue connecting (yes/no)? yes
> root at aws-ovhv-08.avinity.tv's password:
> Welcome to virsh, the virtualization interactive terminal.
> 
> Type:  'help' for help with commands
>        'quit' to quit
> 
> virsh # list
> Id    Name                           State
> ----------------------------------------------------
> 2     tm_vpn                         running
> 3     tmduck                         running
> 22    scsk29funnela                  running
> 25    scsk29procA                    running
> 51    scsk211udc1                    running
> 52    scsk211csm1                    running
> 53    scsk211psm1                    running
> 54    scsk211st1                     running
> 55    tm_admin                       running
> 
> virsh #
> 
> Found the related bug (closed) on Red Hat Bugzilla – Bug 1426573
> 
> On the same bug page, workaround suggested is also applicable.


-- 
Tomáš Golembiovský <tgolembi at redhat.com>