m (Add category) |
m (Add note about incorrect information) |
||
Line 15: | Line 15: | ||
# Login to the autotest server | # Login to the autotest server | ||
# Using the {{command|atest}} command, mark the test system as '''Ready''' | # Using the {{command|atest}} command, mark the test system as '''Ready''' | ||
#: <pre> | |||
#: $ atest host mod -y my-failed-system.example.com | |||
#: Set status to Ready for host: | |||
#: my-failed-system.example.com</pre> | |||
{{admon/warning|Incorrect information|The newer ''autotest-0.12.0'' release no longer supports the above command-line syntax. Investigation into a proper method is underway (see https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000741.html). Please update this section when a conclusion has been reached.}} | |||
[[Category:AutoQA]] | [[Category:AutoQA]] |
Latest revision as of 15:06, 25 June 2010
If for whatever reason, the autotest server has trouble connecting to a client test system, it will first attempt to Repair the system. If the repair operation fails, it will change the system status to Failed. This page documents how to correct systems in a Failed state.
Determine the problem
As always, first determine what the problem is. Is the client test system available
Address problem
Return system to autotest
With the problem resolved, you can tell autotest that the system is once again available for testing.
- Login to the autotest server
- Using the
atest
command, mark the test system as Ready- $ atest host mod -y my-failed-system.example.com
- Set status to Ready for host:
- my-failed-system.example.com