[LU-16804] Exported variable not available in test scripts

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Severity: 3
• Assignee: Sebastien Buisson
• Reporter: Sebastien Buisson

Description

I have a strange behavior with a custom test for the patch https://review.whamcloud.com/c/fs/lustre-release/+/50825.

I specify env=SHARED_KEY=true, and it seems to be taken into account, but not from the beginning. With a grep on the debug traces I added, we can see:

2023-05-03T21:41:51 export SHARED_KEY="true"
2023-05-03T21:41:51 SHARED_KEY=false LGSS_SK= GSS_SK=false
2023-05-03T21:41:51 LGSS_SK=
2023-05-03T21:42:26 trevis-129vm4: SHARED_KEY=false LGSS_SK= GSS_SK=false
2023-05-03T21:42:26 trevis-129vm4: LGSS_SK=
2023-05-03T21:42:26 trevis-129vm5: SHARED_KEY=false LGSS_SK= GSS_SK=false
2023-05-03T21:42:26 trevis-129vm5: LGSS_SK=
2023-05-03T21:42:26 trevis-129vm3: SHARED_KEY=false LGSS_SK= GSS_SK=false
2023-05-03T21:42:26 trevis-129vm3: LGSS_SK=
2023-05-03T21:43:46 SHARED_KEY=true LGSS_SK= GSS_SK=false
2023-05-03T21:43:46 SHARED_KEY=true LGSS_SK= GSS_SK=true
2023-05-03T21:43:56 LGSS_SK=

While we can see "export SHARED_KEY="true"" to start, SHARED_KEY appears to be set to false in function init_test_env(). And later on in init_gss(), it gets proper value.

Any idea why init_test_env() does not see the correct value? Could it be fixed?

Thanks,
Sebastien.