Bug 772539 - Log more details of Cobbler errors
Summary: Log more details of Cobbler errors
Keywords:
Status: CLOSED DUPLICATE of bug 784165
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Steven Lawrance
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 772269
TreeView+ depends on / blocked
 
Reported: 2012-01-09 06:07 UTC by Steven Lawrance
Modified: 2014-08-12 04:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-05 07:57:59 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Steven Lawrance 2012-01-09 06:07:17 UTC 
When a Cobbler power command fails, the system is marked broken but no details of the actual error are logged.  To assist the admins' investigations, we should also record the error string reported and potentially save having to dig up the full Cobbler logs.
Comment 1 Steven Lawrance 2012-01-26 23:33:49 UTC 
I haven't figured out a good way to do this.  We determine success or failure by matching a line in the log with '### TASK COMPLETE' or 'FAILED' respectively.  Preceding that is generally a useless backtrace and 'command failed (rc=1), please validate the physical setup and cobbler config'.  The useful log messages are tricky to pick out because they vary depending on the particular fence agent in use.

So we could either email the entire log to the system owner/admin, or perhaps just leave this for now if we are ditching Cobbler anyway?
Comment 2 Dan Callaghan 2012-06-05 07:57:59 UTC 
The new beaker-provision daemon in version 0.9 reports the return code and stderr of failing power commands, and this info is logged in the system history. (Unfortunately they will often be truncated because of size limits on the system history rows, but that is a separate issue.)

*** This bug has been marked as a duplicate of bug 784165 ***
Note You need to log in before you can comment on or make changes to this bug.