Our customers are still impacted by this connection error between Satellite and libvrt:
Call to virConnectOpen failed: End of file while reading data: Ncat: Connection reset by peer.: Input/output error
Thus, open a BZ for this known upstream issue:
Please increase the following values
#max_anonymous_clients = 20
#max_workers = 20
in /etc/libvirt/libvirtd.conf and restart libvirtd daemon. The libvirt daemon in RHEL is not configured for heavy concurrent client use, we generally do recomment oVirt or Red Hat Enterprise virtualization for enterprise workloads.
An upstream patch to properly close tcp+ssh connections is pending review: https://projects.theforeman.org/issues/14854
Use the workaround from comment 2 as a temporary solution.
Upstream bug assigned to lzap
The patch is still pending review, from my side it should be ready to be merged. I poked my colleague once again to take a look.
Subscribe here for immediate updates: https://github.com/theforeman/foreman/pull/8652
For the record, this bug was fixed and approved into 7.0 testing phase.
Reproducer (tried on my 6.10.2):
Have a Satellite and Libvirt configured on the same machine such that Libvirt can be added to the Satellite as a CR ( http://thomasmullaly.com/2014/08/15/connect-foreman-to-kvm-host-machine/ ).
In `/etc/libvirt/libvirtd.conf`, set `max_clients = 20`.
In `/etc/ssh/sshd_config`, set `ClientAliveInterval 1000`.
In `/etc/foreman/settings.yaml`, set
# systemctl restart libvirtd
# systemctl restart sshd
# foreman-maintain service restart
1) Add the Libvirt to the CR using qemu+ssh scheme
2) Go to Infrastructure -> Compute Resources -> <libvirt> -> Virtual Machines
3) Do 2) once again
=> The first time, the VMs load. The second time, the VMs don't load and after some time, the following error message appears: `There was an error listing VMs: 502 Proxy Error`. In the tailed log, there are NOT the following messages (as expected):
Created libvirt connection <id>: qemu+ssh://root@<fqdn>/system
Terminating libvirt connection <id>: libvirt_connection_qemu+ssh://root@<fqdn>/system
Verified with Sat 7.0 snap 7.0 on RHEL7.
Using the above reproducer, the VMs list always loads no matter how many times I try and the described messages are shown in log.
*** Bug 2090963 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.