Installation fails with error unable to connect to server at '192.168.122.1:16509': Connection refused

[ghost]

Version

eugene@ivantsoft ~/go/src/github.com/openshift/installer (master) $ bin/openshift-install version
bin/openshift-install unreleased-master-99-g4016f5f9c166f255aca875e9d0ba0dffb8c88122

Platform (aws|libvirt|openstack):

libvirt

What happened?

When prompted for the url, I used the default one:

However, the installation fails with

unable to connect to server at '192.168.122.1:16509': Connection refused

What am I doing wrong? None of pre-installation steps showed any errors.

How to reproduce it (as minimally and precisely as possible)?

I went through libvirt guide

[wking]

The issue template asks for a bunch of things that make it easier for us to troubleshoot your issue. Can you add that information?

[ghost]

@wking sorry about that. Issue description updated

[wking]

Can you attach .openshift_install.log (you can cut out all the Terraform stuff if you want, just stuff since Waiting up to 30m0s for the Kubernetes API... should be sufficient)?

[ghost]

log.txt

[wking]

Ah, for some reason I hadn't realized that the connection error was from Terraform:

time="2019-01-18T12:39:09-05:00" level=error msg="Error: Error refreshing state: 1 error occurred:"
time="2019-01-18T12:39:09-05:00" level=error msg="\t* provider.libvirt: virError(Code=38, Domain=7, Message='unable to connect to server at '192.168.122.1:16509': Connection refused')"

You've set up libvirtd to listen?

[wking]

So this is almost certainly not an installer issue. You can test with:

$ virsh -c qemu+tcp://192.168.122.1/system version
Compiled against library: libvirt 3.9.0
Using library: libvirt 3.9.0
Using API: QEMU 3.9.0
Running hypervisor: QEMU 2.9.0

I expect that to give you:

error: failed to connect to the hypervisor
error: unable to connect to server at '192.168.122.1:16509': Connection refused

instead. Then work through our libvirt docs and/or your system's libvirt docs until you get virsh connecting over TCP. Once you have that straightened out, I expect the installer will work.

[ghost]

@wking yes, it was misconfiguration on my side. Closing the issue. However, I was not able to install again since the installer never got console route. I think I hit #1078

[ScrapCodes]

Hi, the links to the docs above are now 404. I am hitting the same problem, it would be helpful, if you could share those docs.