Description of problem: On out of the box installation of Fedora 32 libvirtd activated via tcp socket will listen only on the ipv6(via systemd) Version-Release number of selected component (if applicable): libvirt-daemon-6.1.0-4.fc32.x86_64 systemd-245.7-1.fc32.x86_64 kernel-5.8.6-201.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. dnf install libvirt-daemon-kvm libvirt-client 2. systemctl enable --now libvirtd-tcp.socket 3. netstat -patun | grep 16509 Actual results: tcp6 0 0 :::16509 :::* LISTEN 1/systemd For the record there is nothing on ipv4 that could be libvirtd/systemd listening . Expected results: Systemd/libvirtd is listening on both ipv4 and ipv6. Something like this tcp 0 0 0.0.0.0:16509 :::* LISTEN 1/systemd tcp6 0 0 :::16509 :::* LISTEN 1/systemd Additional info: Masking off the socket activation and reverting to --listed and appropriate config changes(enabling the sockets,...) workarounds this issue. Host has both ipv4 and ipv6 address assigned.
libvirts builtin listening code sets IPV6_V6ONLY=1, and thus needs to explicitly listen on both IPv4 and IPv6 addresses. I expect systemd relies on the Liinux default IPv6_V6ONLY=0 and thus only needs an IPv6 socket, which is also able to accept IPv4 conections IOW, looking at the netstat output is not a good test. You need to actually verify whether you can connect a client over IPv4.
The issue it that I/openshift-installer can't connect over ipv4. For the whole context I have hit this when trying to install OKD with libvirt backend. With switching back to the the --listen and the config it works.
What are the proper steps to verify that the ipv4 is working correctly, with the socket setup?
telnet is a better way to test if a port is accepting connections Using Fedora 32 libvirt-daemon-6.1.0-4.fc32.x86_64 and the TCP socket # systemctl start libvirtd-tcp.socket # netstat -t -a -n -p | grep 16509 tcp6 0 0 :::16509 :::* LISTEN 1/systemd # telnet 127.0.0.1 16509 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. ^] telnet> Connection closed. # telnet ::1 16509 Trying ::1... Connected to ::1. Escape character is '^]'. ^] telnet> Connection closed. # telnet 192.168.1.163 16509 Trying 192.168.1.163... Connected to 192.168.1.163. Escape character is '^]'. ^] telnet> Connection closed. This shows it is working ok in normal circumstances. Has something set net.ipv6.bindv6only=1 on your host, as that would break this.
Interesting via telnet it gets activated but the installer(AFAIK actually terraform) will not activate the libvirtd. I'm really curious what might be the issue. Firewall is open for libvirtd port.
So the local telnet test shows systemd is correctly listening for connections. Are there any network namespaces involved here ? Make sure you're testing "telnet" from the same execution context wrt namespaces / hosts, as you run terrafrom from.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.