[LU-19436] ip2nets yaml parsing doesn't adhere to documented behavior

• Type: Bug
• Resolution: Fixed
• Priority: Medium
• Fix Version/s: Lustre 2.17.0
• Severity: 3
• Assignee: Chris Horn
• Reporter: Chris Horn

Description

There are still a few issues with the ip2nets yaml parsing. In particular, it doesn't adhere to the documented behavior of only applying the first matching rule per network.

The following entry is placed in the lustre.conf file on each server and client:

options lnet 'ip2nets="tcp0(eth0) 192.168.0.[2,4]; \
tcp0 192.168.0.*; o2ib0 132.6.[1-3].[2-8/2]"'
Each entry in ip2nets is referred to as a 'rule'.

The order of LNet entries is important when configuring servers. If a server node can be reached using more than one network, the first network specified in lustre.conf will be used.

Because svr1 and svr2 match the first rule, LNet uses eth0 for tcp0 on those machines. (Although svr1 and svr2 also match the second rule, the first matching rule for a particular network is used).

(emphasis mine)

Issue Links

• is related to: LU-19554 sanity-lnet test_153: FAIL: Import failed with rc = 234
• is related to: LU-18417 Finish IPv6 support