hornc, simmonsja,
we need to add a default test session that is running with IPv6 enabled, otherwise we are not getting any test coverage for this new code.

I'm thinking that it makes sense to add a session like review-ldiskfs (sanity + sanity-lnet) with FORCE_LARGE_NID=true set, so that it will run with IPv6 NIDs. Is there anything else that is needed to run an IPv6 test session? I see some patches are also setting LOAD_MODULES_REMOTE=true, is this also required for IPv6 testing? Initially this should be an optional session, but should be moved to enforced once it is passing consistently. Ticket assigned to hornc until we can get enough information to pass this on to colmstea to set up the Autotest session(s).

Have you ever run a full conf-sanity.sh session (in Autotest or manually) with FORCE_LARGE_NID=true to see what is working and what is broken with IPv6 enabled? Same with other test scripts (e.g. sanity-sec, sanity-hsm, etc.) to see what is working and where work is still needed? I only see a few always_except lines in sanity-lnet.sh checking FORCE_LARGE_NID, so this makes me worried that there may be large parts of Lustre functionality that have never been tested with IPv6 at all?

Probably it is worthwhile a one-time running of full-part-1, full-part-2, full-part-3 sessions with FORCE_LARGE_NID=true to get a full set of results. At that point we can assess where remaining gaps in functionality and/or testing need to be addressed.

CC: srevankar, ksolanki, colmstea, achittibabu, ssmirnov for visibility until we know what needs to be configured to run these sessions