Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

NVMe-cli 2.x breaks NVMeOF connection at least with TCP protocol, when issuing connect-all command. Manual connection (discover target NQN and target IP addresses, use single controller connect commands) works.


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

libnvme-1.4

Steps to Reproduce:
1. example: nvme connect-all -t tcp -a 172.168.25.64   -s 4420

Actual results:

Failed to write to /dev/nvme-fabrics: Invalid argument
failed to connect controller, error 1006
Failed to write to /dev/nvme-fabrics: Invalid argument
failed to connect controller, error 1006
Failed to write to /dev/nvme-fabrics: Invalid argument
failed to connect controller, error 1006
Failed to write to /dev/nvme-fabrics: Invalid argument
failed to connect controller, error 1006

dmesg:

[ 8045.246675] nvme_fabrics: unknown parameter or missing value 'tls' in ctrl creation request
[ 8045.246707] nvme_fabrics: unknown parameter or missing value 'tls' in ctrl creation request
[ 8045.246719] nvme_fabrics: unknown parameter or missing value 'tls' in ctrl creation request
[ 8045.246730] nvme_fabrics: unknown parameter or missing value 'tls' in ctrl creation request


Expected results:


Additional info:

Hello

If you provide the package you want me to test I can test it.

I already validated the fix from Chris Leech so I am actually happy for you to just say tested by CEE

~~~
From the other bug
This is a known issue
The TLS issue, I already reported in the other case is well known now and we have a fix.

We have it working now with no issues with a test package I got from Chris Leech.
https://github.com/linux-nvme/libnvme/issues/612

Run rpm -Uvh libnvme-1.2-2.1.test.el9_2.x86_64.rpm
~~~

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 (libnvme 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/RHEA-2023:6603

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days