[LU-19733] Don't use NIDs on missing networks

• Type: Bug
• Resolution: Unresolved
• Priority: Medium
• Severity: 3
• Assignee: Mikhail Pershin
• Reporter: Mikhail Pershin

Description

In setups where client configured networks are subset of servers networks, e.g. for multi-tenancy, there is problem with client trying to use NIDs on missing networks, getting them from config files or IR. Patch prevents that in two ways:

• LNet skips peer creation from Lustre calls if network is missing
• Lustre doesn't populate internal connection/NIDs structures with NIDs on missing networks

Both means keep only NIDs on configured networks for further use. This implements effectively NID filtering by networks on client side

Issue Links

• is related to: LU-19734 mgc_apply_recover_logs() to check import instances immediately