Bug #8078
If a command execution fails the state should be changed to "undefined"
| Status: | Resolved | Start date: | 2010-06-07 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Tobias Liebig | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Currently a failed command execution (noc connection, invalid request, timeout) triggers an error. But it should really be an undefined result because otherwise errors will be sent without knowing that the test failed. This always causes some noise in the notification mails for us.
Related issues
| related to Caretaker - Task #12988: Set Test-Result to Undefined, if RemoteCommand has a timeout | Resolved | 2011-02-11 |
Associated revisions
[+TASK] caretaker_instance: Set Test-Result to Undefined, if RemoteCommand has a timeout (resolves #12988, resolves #8078 )
[+FEATURE] caretaker_instance: Status of CommandResult is now differentially (OK, ERROR, UNDEFINED, ..) instead of just TRUE or FALSE. behaves backwards-compatible
[+TASK] caretaker_instance: cleanups and some minor internal refactoring
History
Updated by Tobias Liebig over 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r43816.