Description of problem: During the deployment phase, a user should be able to connect to the VM console using gnu+tls. However, certificates are missing (see bug 1034634), and after generating it manually, still unable to connect to the console. Version-Release number of selected component (if applicable): IS24.2 How reproducible: Try connecting: virsh -c qemu+tls://some-host/system console HostedEngine Actual results: error: unable to connect to server at 'sla-sheldon:16514': Connection refused error: failed to connect to the hypervisor Expected results: Should connect to console Additional info: it seems that libvirt is not listening to tls: netstat -ap --ip | grep libv tcp 0 0 *:16509 *:* LISTEN 3402/libvirtd libvirtd.conf updated by vdsm has: listen_tcp=1 listen_tls=0 ## end of configuration section by vdsm-4.10.3
Doron, you probably meant "qemu+tls" and perhaps in some cases "gnutls" (no "+").
(In reply to Yedidyah Bar David from comment #2) > Doron, you probably meant "qemu+tls" and perhaps in some cases "gnutls" (no > "+"). Right, I was using associations...
isn't this a dup of bug 1034634?
tls port is not listening because the required certificate is not generated by hosted-engine --deploy. It's generated later by ovirt-host-deploy when the host is added to the engine. *** This bug has been marked as a duplicate of bug 1034634 ***