+32
−4
Loading
It's been noticed that the backoff of 1s may be not enough for the
net devices to pop up back under the main namespace. Scenario like
this may look similar to:
[2023-11-24T13:25:56.234Z] 14:25:56 -- nvmf/common.sh@398 -- # remove_spdk_ns
...
[2023-11-24T13:26:02.498Z] Found 0000:af:00.0 (0x8086 - 0x159b)
...
[2023-11-24T13:26:02.498Z] Found 0000:af:00.1 (0x8086 - 0x159b)
...
[2023-11-24T13:26:02.498Z] No net devices associated with 0000:af:00.0
...
[2023-11-24T13:26:02.498Z] Found net devices under 0000:af:00.1: eth3
...
[2023-11-24T13:26:02.498Z] ========== Backtrace start: ==========
[2023-11-24T13:26:02.498Z] 230 # We need two net devs at minimum
[2023-11-24T13:26:02.498Z] => 231 ((${#TCP_INTERFACE_LIST[@]} > 1))
...
After closer inspection the 0000:af:00.0's eth* device normally would
be picked up as $NVMF_TARGET_INTERFACE but since it's still under the
eth*_ns_spdk namespace (from the previous test) it cannot be found
under the main namespace.
To mitigate, wait until all net devices are visible under main
namespace's sysfs.
Change-Id: If190abb6a98b42321bef945979ed1bacbafcf2ce
Signed-off-by:
Michal Berger <michal.berger@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20737
Reviewed-by:
Karol Latecki <karol.latecki@intel.com>
Reviewed-by:
Jim Harris <jim.harris@samsung.com>
Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com>