minion: improve logging when execution fails
ClosedPublic

Authored by kparal on Mar 14 2016, 12:34 PM.

Details

Summary

tiny logging change, but improves readability when something went wrong. It's clearer that the minion image is getting shut down prematurely and the error occurred before that, not after that.

Before:

[libtaskotron] 16:41:33 INFO    Running task on a disposable client using libvirt...
[libtaskotron] 16:41:33 INFO    Creating VM for task
[libtaskotron] 16:41:33 INFO    Shutting down the minion...
[libtaskotron] 16:41:33 ERROR   Was expecting to find instance taskotron-20160311_164132_907710 but it does not already exist

After:

[libtaskotron] 11:39:02 INFO    Running task on a disposable client using libvirt...
[libtaskotron] 11:39:02 INFO    Creating VM for task
[libtaskotron] 11:39:02 WARNING Task execution was interrupted by an error, doing emergency cleanup.
[libtaskotron] 11:39:02 INFO    Shutting down the minion...
[libtaskotron] 11:39:02 ERROR   Was expecting to find instance taskotron-20160314_113902_585744 but it does not already exist
Test Plan

ran test suite, tried manually with a bug

Diff Detail

Repository
rLTRN libtaskotron
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
kparal retitled this revision from to minion: improve logging when execution fails.Mar 14 2016, 12:34 PM
kparal updated this object.
kparal edited the test plan for this revision. (Show Details)
kparal added a reviewer: mkrizek.
mkrizek accepted this revision.Mar 14 2016, 12:58 PM
This revision is now accepted and ready to land.Mar 14 2016, 12:58 PM
This revision was automatically updated to reflect the committed changes.