Better log information when CLIs fails
Most of the time, when a CLI fails, the info level converge log as something like this:
Mixlib:
Expected process to exit with [0], but received '1'
Without re-running with debug it can be difficult to understand the issue.
Work items to consider
- Tweak the new Common CLI method to handle error logging in better ways.
- Maybe always log command being executed?
- Maybe always log stdout/stderr when a command fails
- Maybe, based upon project, grab last ## lines from /var/logs/
- tweak cookbooks to use the new Common CLI methods instead of each having their own way of doing this.
Blueprint information
- Status:
- Complete
- Approver:
- Justin Shepherd
- Priority:
- Medium
- Drafter:
- Mark Vanderwiel
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- Accepted for juno
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Mark Vanderwiel
Related branches
Related bugs
Sprints
Whiteboard
Closing this out as we are moving toward a new client cookbook to handle this instead of using CLIs in a Common library.
