| Summary: | Log more details of Cobbler errors | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Steven Lawrance <stl> |
| Component: | scheduler | Assignee: | Steven Lawrance <stl> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.8 | CC: | bpeck, dcallagh, mcsontos, rmancy, stl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-05 07:57:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 772269 | ||
|
Description
Steven Lawrance
2012-01-09 06:07:17 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? 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 *** |