Red Hat Bugzilla – Bug 1020851
Unsetting ARCH breaks task execution
Last modified: 2016-05-31 21:49:00 EDT
Description of problem: It seems that test harness is unable to handle situation when the ARCH parameter with empty value is provided to the task. I believe the harness should not be sensitive to such common env parameter. Version-Release number of selected component (if applicable): 0.14.1 Steps to Reproduce: <task name="/CoreOS/wget/Sanity/download" role="None"> <params> <param name="ARCH" value=""/> </params> </task> Actual results: No handlers could be found for logger "rhts_task" Expected results: Task successfully executed.
This is actually rhts-test-runner.sh that causes the problem, and throws the error if the string is null. rhts-environment.sh will actually fix this by assigning the result of 'uname -i' to the ARCH var if it is a null string, but the problem is that rhts-environment.sh is not called until _after_ rhts-test-runner.sh tests ARCH and throws this error. The best solution may be to always call rhts-environment first. In fact if we do that we may even be able to get rid of those sanity checkers (not sure).