Mellanox / network-operator-init-container / 24441944588

57%

main: 65%

Pull #103

github

Add storage module detection and mlx5 prefix greenlisting to
pre-flight checks

The init container's module dependency checker now classifies
blocking dependencies into four tiers instead of three:

1a. Known third-party RDMA modules → recommend
    UNLOAD_THIRD_PARTY_RDMA_MODULES=true
1b. Known storage-over-RDMA modules (ib_isert, nvme_rdma,
    nvmet_rdma, rpcrdma, xprtrdma, ib_srpt) → recommend
    UNLOAD_STORAGE_MODULES=true (new)
2.  Unknown kernel modules → manual intervention
3.  Userspace processes → manual intervention

Previously storage modules fell into category 2, producing a
misleading "manually unload or blacklist" message when the user
just needs to set UNLOAD_STORAGE_MODULES=true. The driver
container already checks and blocks on these modules — the init
container now gives the same actionable guidance earlier, before
the driver container starts.

Modules with an "mlx5" prefix (e.g. mlx5_vdpa, mlx5_netdev) are
now silently greenlit. These are NVIDIA's own modules that may
depend on mlx5_core but are not in the configured MOFED module
list — they should never be reported as blocking.

Signed-off-by: Alexander Maslennikov <amaslennikov@nvidia.com>

18 of 36 new or added lines in 2 files covered. (50.0%)

313 of 553 relevant lines covered (56.6%)

9.97 hits per line