-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.1
-
None
-
nvme-cli-2.13-2.el10
-
No
-
Important
-
ZStream
-
rhel-storage-io-2
-
18
-
1
-
False
-
False
-
-
None
-
None
-
Regression Exception
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
With RHEL-10.1, when issuing a 'nvme list-subsys', the persistent discovery controller is now present:
# nvme list-subsys nvme-subsys0 - NQN=nqn.1992-08.com.netapp:sn.54c8bee1db9a11ecbff200a098cbcac6:discovery hostnqn=nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0048-4810-8054-b7c04f593233 \ +- nvme0 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ef00a098cbcac6,host_traddr=nn-0x20000024ff19bb62:pn-0x21000024ff19bb62 live +- nvme1 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ec00a098cbcac6,host_traddr=nn-0x20000024ff19bb62:pn-0x21000024ff19bb62 live +- nvme3 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ed00a098cbcac6,host_traddr=nn-0x20000024ff19bb63:pn-0x21000024ff19bb63 live +- nvme5 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ee00a098cbcac6,host_traddr=nn-0x20000024ff19bb63:pn-0x21000024ff19bb63 livenvme-subsys2 - NQN=nqn.1992-08.com.netapp:sn.54c8bee1db9a11ecbff200a098cbcac6:subsystem.nvme_1 hostnqn=nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0048-4810-8054-b7c04f593233 \ +- nvme2 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ec00a098cbcac6,host_traddr=nn-0x20000024ff19bb62:pn-0x21000024ff19bb62 live +- nvme4 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ef00a098cbcac6,host_traddr=nn-0x20000024ff19bb62:pn-0x21000024ff19bb62 live +- nvme6 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ed00a098cbcac6,host_traddr=nn-0x20000024ff19bb63:pn-0x21000024ff19bb63 live +- nvme7 fc traddr=nn-0x20eb00a098cbcac6:pn-0x20ee00a098cbcac6,host_traddr=nn-0x20000024ff19bb63:pn-0x21000024ff19bb63 live
We did not see this with RHEL-9.7 and nvme-cli-2.13-1.el9:
# uname -r 5.14.0-585.el9.x86_64 # rpm -qa nvme-cli nvme-cli-2.13-1.el9.x86_64 # nvme list-subsys nvme-subsys1 - NQN=nqn.1992-08.com.netapp:sn.4cd37e89c7e211ecb5b300a098cbcac6:subsystem.nvme_1 hostnqn=nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0033-4d10-8032-b5c04f354b33 \ +- nvme1 fc traddr=nn-0x20dd00a098cbcac6:pn-0x20de00a098cbcac6,host_traddr=nn-0x200000109b579dc6:pn-0x100000109b579dc6 live +- nvme2 fc traddr=nn-0x20dd00a098cbcac6:pn-0x20e100a098cbcac6,host_traddr=nn-0x200000109b579dc6:pn-0x100000109b579dc6 live +- nvme5 fc traddr=nn-0x20dd00a098cbcac6:pn-0x20df00a098cbcac6,host_traddr=nn-0x200000109b579dc7:pn-0x100000109b579dc7 live +- nvme7 fc traddr=nn-0x20dd00a098cbcac6:pn-0x20e000a098cbcac6,host_traddr=nn-0x200000109b579dc7:pn-0x100000109b579dc7 live
Please provide the package NVR for which the bug is seen:
- rpm -qa nvme-cli
nvme-cli-2.11-5.el10.x86_64
- links to
-
RHBA-2025:150124
nvme-cli bug fix and enhancement update
