[LU-16822] test IPv6 NIDs in sanity-lnet.sh

• Type: Improvement
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.16.0
• Labels: IPv6
• Severity: 3
• Assignee: James A Simmons
• Reporter: Andreas Dilger

Description

It should be possible to add test cases to sanity-lnet.sh that are using IPv6 addresses that are (probably) already being assigned to the test nodes in autotest.

As a starting point, a patch that is adding a new test_0 that is just printing out the interfaces configured in the VM node with ifconfig (or new-fangled alternative) would give us useful information and not be harmful in the future.

At that point, if the client and MDS/OSS nodes have IPv6 addresses assigned, it should be possible to add subtests that are configuring IPv6 NIDs:

• use lnetctl to add IPv6 NIDs to a node
• use lnetctl ping to ping the local and peer NIDs with IPv4 and IPv6 addresses to see all NIDs reported
• configure and run lnet selftest with the IPv6 NIDs
• etc.
• unconfigure IPv6 NIDs from the nodes

I suspect that this can be done without any changes to autotest, since sanity-lnet.sh is unmounting Lustre anyway, and there should already be enough IPv6 infrastructure on master to test at the LNet level.

Issue Links

• is related to: LU-17889 Autotest nodes should not use 'fe80:' link local (loopback) IPv6 address
• is related to: LU-17986 Update sanity-lnet test 111 for IPv6
• is related to: LU-10391 LNET: Support IPv6