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 connecting to an NBD server over TLS, the shutdown of the
connection (nbd_shutdown) fails with:

nbd_shutdown: gnutls_record_recv: The TLS connection was non-properly terminated.

Version-Release number of selected component (if applicable):

libnbd-1.12.5-1.el9

How reproducible:

100%

Steps to Reproduce:

1. Set up a qemu-nbd + TLS server using steps 1.-4. of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2111524

2. Run one of these commands against the server:

$ nbdsh -c 'h.set_tls_certificates("/var/tmp/pki")' -c 'h.connect_uri("nbds://foo")' -c 'h.shutdown()'
nbdsh: command line script failed: nbd_shutdown: gnutls_record_recv: The TLS connection was non-properly terminated.

$ nbdcopy nbds://foo?tls-certificates=/var/tmp/pki null:
nbds://foo?tls-certificates=/var/tmp/pki: nbd_shutdown: gnutls_record_recv: The TLS connection was non-properly terminated.

Upstream fix:
https://listman.redhat.com/archives/libguestfs/2022-July/029545.html
https://listman.redhat.com/archives/libguestfs/2022-July/029546.html

Reproduce with 
qemu-img-7.0.0-9.el9.x86_64
libnbd-1.12.5-1.el9.x86_64

Steps to Reproduce:
1. Set up a qemu-nbd + TLS server using steps 1.-4

2. Run one of these commands against the server

# nbdsh -c 'h.set_tls_certificates("/var/tmp/pki")' -c 'h.connect_uri("nbds://10.73.178.63")' -c 'h.shutdown()'
nbdsh: command line script failed: nbd_shutdown: gnutls_record_recv: The TLS connection was non-properly terminated.



Verified with 
qemu-img-7.0.0-9.el9.x86_64
libnbd-1.12.6-1.el9.x86_64

Steps:
1. Set up a qemu-nbd + TLS server using steps 1.-4

2.  Run one of these commands against the server:

# nbdsh -c 'h.set_tls_certificates("/var/tmp/pki")' -c 'h.connect_uri("nbds://10.73.178.63")' -c 'h.shutdown()'
#
# nbdcopy nbds://10.73.178.63?tls-certificates=/var/tmp/pki null:
#


Mark Verified:Tested. Moving to VERIFIED.

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 (libnbd bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:7944