Bug 1020851
| Summary: | Unsetting ARCH breaks task execution | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Petr Šplíchal <psplicha> |
| Component: | beah | Assignee: | beaker-dev-list |
| Status: | CLOSED EOL | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | develop | CC: | ksrot, mastyk, ohudlick, qwan, tools-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-11 12:16:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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). Beah is no longer supported by Beaker development team. Instead of that, we are working on Restraint test harness. You can find all the features of Restraint here. https://restraint.readthedocs.io/en/latest/ If you think your RFE should be still implemented as part of Restraint feel free to create a new BZ ticket. https://bugzilla.redhat.com/enter_bug.cgi?product=Restraint In case you have any question feel free to reach out to me Thank you, Martin Styk <martin.styk> |
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.