Bug 1376318 - engine-backup's log is not detailed enough
Summary: engine-backup's log is not detailed enough
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backup-Restore.Engine
Version: 4.0.3
Hardware: Unspecified
OS: Unspecified
low
medium vote
Target Milestone: ---
: ---
Assignee: Yedidyah Bar David
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 05:16 UTC by Yedidyah Bar David
Modified: 2022-02-25 08:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-25 07:29:46 UTC
oVirt Team: Integration

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44913 0 None None None 2022-02-25 08:26:25 UTC

Description Yedidyah Bar David 2016-09-15 05:16:08 UTC 
Description of problem:

Sometimes the log generated by engine-backup is not enough for debugging failures.

Due to the fix to bug 1172191 it's somewhat difficult to cause it to produce extra debugging information.

We probably want to make it export OTOPI_DEBUG=1 for the calls to ovirt-engine-provisiondb.

We probably want to run it with 'set -x', but also need to consider using BASH_XTRACEFD with some other file descriptor, as in some places we analyze stderr of some commands. This will make it bash-specific. Another option which might be more complex but more portable is to 'set +x' before such commands.

Depending on the solution, it might make sense to make this optional, e.g. only when a flag '--debug' is passed.
Comment 1 Yaniv Lavi 2018-06-25 07:29:46 UTC 
Closing old bugs.
Please reopen if still relevant.
Patches are welcomed.
Note You need to log in before you can comment on or make changes to this bug.