The shared key feature (SSK) new in Lustre is not currently passing all tests in some suites within the Lustre test environment. When SHARED_KEY is set to TRUE, the suites and tests listed below cause errors, some of which disrupt further tests. This LU is meant to track these issues and link to the appropriate fixes, if they exist. The testing feature for SSK was added as part of
Some tests may fail because of defects in the SSK feature, but it is also possible that they fail because the current testing framework fails to account for them properly. For example, there may be timing issues related to long SSK spin-up that prevent steps from being resolved in their proper order.
Current tests which are known to cause issues include:
sanity: 101g 102b 300f
sanity-gss: 8 90
dne_sanity: 6g 27u 27D 27E 33f 83 101g 102b 102c 102i 102k 102m 102n 102r 103b 105a 105b 105c 106 110
replay-single: 71a 110f
replay-dual: 0a 0b
conf-sanity: 76a 76b 76c 76d 103
sanity-lfsck: 18e 33
If the defects cannot be resolved, they will be added as exceptions to the testing suites, but only if SSK is enabled.