If a command execution fails the state should be changed to "undefined"
|Priority:||Should have||Due date:|
|Assignee:||Tobias Liebig||% Done:||
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 to Caretaker - Task #12988: Set Test-Result to Undefined, if RemoteCommand has a timeout||Resolved||2011-02-11|
[+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