Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Lustre 2.16.0
-
None
-
Maloo test bed nodes
-
3
-
9223372036854775807
Description
Pushing patches to run sanity-lnet test with IPv6 which are working locally for me to maloo revealed that the IPv6 address setup is only local link (fe80:.....). These addresses are only visible to the local node so the more complex LNet test can't run. Also LNet ignores these addresses. Proper IPv6 addresses need to be setup.
mkvardakov, looking at the following test runs from James' patch:
https://testing.whamcloud.com/test_sets/3c1e5454-23e2-4162-958c-af443ed4fde3
https://testing.whamcloud.com/test_sets/9f145a47-09f3-4494-a094-d27ea661de38
I see the following listed near the start of the sanity-lnet.suite_log.onyx-116vm1.log file, from the output of "do_lnetctl net show" and "ip a":
so it looks like the inet6 address assignments are still using the link-local fe80:: range instead of the fd33:3981:3213: ranges that you mention above for onyx and trevis? Is there something that needs to be specified for an IPv6 test session to assign these non-local addresses? Is there a reason that shouldn't be done automatically for all test sessions?