RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When setting keepalive_required=1, libvirtd will refuse all the clients even if the client supports keepalive.

Version-Release number of selected component :
libvirt-1.2.17-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Set keepalive_required=1 in libvirtd.conf on host A, restart libvirtd service.

2.Connect to the libvirtd of host A:
# virsh -c qemu+tcp://10.66.6.6/system
error: failed to connect to the hypervisor
error: operation failed: keepalive support is required to connect


Actual results:
As step2, libvirtd refused the client connection.

Expected results:
As virsh client supports replying for server keepalives, it should connect successfully.

Patch proposed upstream:

https://www.redhat.com/archives/libvir-list/2015-July/msg00738.html

Fixed upstream by v1.2.18-61-ga8743c39389b:

commit a8743c39389b76897811f60dcd8485cd51d76f02
Author: Martin Kletzander <mkletzan>
Date:   Mon Jul 20 14:51:24 2015 +0200

    rpc: Remove keepalive_required option

Verify this bug with libvirt-1.2.17-6.el7, could found the clear explanation that the keepalive_required option has been removed in libvirtd.conf, also found the corresponding code has been disabled, so we could verify this bug right now. 

# These configuration options are no longer used.  There is no way to
# restrict such clients from connecting since they first need to
# connect in order to ask for keepalive.
#
#keepalive_required = 1
#admin_keepalive_required = 1

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2202.html