Attaching NVMe-oF no longer works in CentosOS 9 stream using nvme 2.4
and libnvme 1.4.
The reason is that the 'address' file in sysfs now has the 'src_addr'
information.
Before we had: traddr=127.0.0.1,trsvcid=4420 After:
Now we have: traddr=127.0.0.1,trsvcid=4420,src_addr=127.0.0.1
This patch fixes this issue and future proofs for any additional
information that may be added by parsing the contents and searching for
the parts we care: destination address and port.
Closes-Bug: #2035811
Change-Id: I7a33f38fb1b215dd23e2cff3ffa79025cf19def7
(cherry picked from commit 268b1261ecf142c9ef603af2ff62815f9670e5d0)
(cherry picked from commit 05bcadc935fce5a199ccd30ccfe6ed795900112e)
Reviewed: https:/ /review. opendev. org/c/openstack /os-brick/ +/905992 /opendev. org/openstack/ os-brick/ commit/ b1363ca36a34225 f4ae6e4e835f504 249479dd16
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit b1363ca36a34225 f4ae6e4e835f504 249479dd16
Author: Gorka Eguileor <email address hidden>
Date: Tue Sep 12 15:12:12 2023 +0200
NVME-oF: Fix to support new "address" in sysfs
Attaching NVMe-oF no longer works in CentosOS 9 stream using nvme 2.4
and libnvme 1.4.
The reason is that the 'address' file in sysfs now has the 'src_addr'
information.
Before we had:
traddr= 127.0.0. 1,trsvcid= 4420 After:
Now we have:
traddr= 127.0.0. 1,trsvcid= 4420,src_ addr=127. 0.0.1
This patch fixes this issue and future proofs for any additional
information that may be added by parsing the contents and searching for
the parts we care: destination address and port.
Closes-Bug: #2035811 dd23e2cff3ffa79 025cf19def7 9ef603af2ff6281 5f9670e5d0) 199ccd30ccfe6ed 795900112e)
Change-Id: I7a33f38fb1b215
(cherry picked from commit 268b1261ecf142c
(cherry picked from commit 05bcadc935fce5a