Open LiaoU3 opened 4 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1332.
This message was autogenerated
Upon initial analysis, this seems to be caused by plainbox.impl.execution.get_differential_execution_environment, if the user is switched all environment variables not explicitly set in the job env session or that don’t follow some arbitrary name are removed from the propagated environment. I don’t know why this is done, this needs more investigation.
Bug Description
Description
I found that
$CHECKBOX_RUNTIME
is having wierd behavior with the fieldenviron
anduser
in remote and local run, so I performed some experiment to check the outcome.Test Method
I test remote and local run indiviually, with or without
environ
and with or withoutuser: root
. To check if under the conditions below if a job could get$CHECKBOX_RUNTIME
this variable.Remote run
Local run
Conclusion
In remote run
According to this page in checkbox tutorial,
environ
should be optional. However, when it comes to$CHECKBOX_RUNTIME
, it seems like this field becomes mandatory.In local run
It is such a mess because a root user is not able to get
$CHECKBOX_RUNTIME
withoutenviron
provided.My suspect
I suspect that
$CHECKBOX_RUNTIME
is only visible by root user. That's why we got the results in remote run. Nevertheless, in local run, I have completely no idea why this is happeneing.Submission:
Jira link
https://warthogs.atlassian.net/browse/OEMQA-4114
To Reproduce
Environment
Relevant log output
Additional context
No response