[LU-8913] nodemap: wildcard '*@<net>' is broken

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.0, Lustre 2.10.4
• Affects Version/s: Lustre 2.9.0
• Environment: CentOS 7.2, Lustre-2.8.60
• Severity: 3
• Assignee: Emoly Liu
• Reporter: Stephane Thiell

Description

Hi, this is a minor bug report for nodemap. The nodemap documentation indicates that wildchar is allowed:

<nidrange>      :== <addrrange> '@' <net>
<addrrange>     :== '*' |
                        <ipaddr_range> |
                        <numaddr_range>

but it doesn't seem to work as expected, as it just adds a single IP 0.0.0.0:

$ cat /proc/fs/lustre/nodemap/sherlock/ranges
[

]
$ lctl nodemap_add_range --name sherlock --range '*@o2ib3'
$ cat /proc/fs/lustre/nodemap/sherlock/ranges
[
 { id: 18, start_nid: 0.0.0.0@o2ib3, end_nid: 0.0.0.0@o2ib3 }
]

As a workaround, we can use [0-255].[0-255].[0-255].[0-255]@o2ib3, in that case the full range of IP is added:

[
 { id: 19, start_nid: 0.0.0.0@o2ib3, end_nid: 255.255.255.255@o2ib3 }
]

Note: Four wildchars separated by dots also work but I don't believe it should according to the documentation.

Thanks,
Stephan