Bug 2128081

Summary: nvme-cli: nvme connect-all returns "skipping unsupported subtype 3"
Product: Red Hat Enterprise Linux 8 Reporter: Marco Patalano <mpatalan>
Component: nvme-cliAssignee: Maurizio Lombardi <mlombard>
Status: NEW --- QA Contact: Zhang Yi <yizhan>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.7Keywords: Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2089955    

Description Marco Patalano 2022-09-19 19:23:48 UTC 
Description of problem: When issuing an "nvme connect-all" to a target running OnTap 9.11, I am seeing the following:

skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
traddr=172.16.1.102 is already connected
traddr=172.16.0.102 is already connected
traddr=172.16.1.101 is already connected
traddr=172.16.0.101 is already connected
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
traddr=172.16.1.101 is already connected
traddr=172.16.0.101 is already connected
traddr=172.16.1.102 is already connected
traddr=172.16.0.102 is already connected
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
skipping unsupported subtype 3
traddr=172.16.1.101 is already connected
traddr=172.16.0.101 is already connected
traddr=172.16.1.102 is already connected
traddr=172.16.0.102 is already connected

This was observed with nvme-cli-1.16-5.el8 and can be seen in the following job:

https://beaker.engineering.redhat.com/jobs/6996650

Below are the contents of my discovery.conf:

-t tcp -a 172.16.0.101 -s 4420
-t tcp -a 172.16.1.101 -s 4420
-t tcp -a 172.16.0.102 -s 4420
-t tcp -a 172.16.1.102 -s 4420

FYI, the connection to the namespaces are not impacted.

Version-Release number of selected component (if applicable):
nvme-cli-1.16-5.el8

How reproducible:
Often

Steps to Reproduce:
1. issue nvme connect-all