Hide Forgot
Description of problem: I am not able to run LC without asking questions AND get verbose output. There is --quite parameter which reduces questions but doesn't generate any output. I would like to get logs/errors on STDERR and outputs/results (table or the path to file which contains collected logs) on STDOUT. There is also --verbose option, which IMHO should exclude mutually with --quite, but anyway when I use both it doesn't ask questions, but the outputs goes to log-file, which is cleaned at start of every application run. Version-Release number of selected component (if applicable): ovirt-engine-log-collector-3.0.0_0001-1.6.fc16.x86_64 How reproducible: # asks questions rhevm-log-collector -p PASWORD --pg-pass PASSWORD collect # no question, without outputs rhevm-log-collector -p PASWORD --pg-pass PASSWORD --quite collect # no question, but outputs in log-file rhevm-log-collector -p PASWORD --pg-pass PASSWORD --quite --verbose collect Actual results: no outputs or asking questions Expected results: don't ask questions and generate output as unix-like programs does (stdout && stderr) Additional info:
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
The following question, that appear when hosts exist, and running engine-log-collector collect, prevents automatic test to run the log-collector, with collecting host logs: 'About to collect information from 1 hypervisors. Continue? (Y/n)' In order to resolve this we can, for example, Set log-collector to not collecting host logs by default, and if user wishs to do so, add an option for that.
or support -y to answer yes to questions?
So, this bug requests are: - --quiet and --verbose should be mutually exclusive - log/errors to stderr, output/results to stdout (bug #956518) - use different log files for each execution avoiding to clean the same log at start of every application run - support -y, --assumeyes (like yum) to answer yes to questions or -u, --unattended (like engine-cleanup) avoiding to ask Continue / Confirm questions. correct?
(In reply to Sandro Bonazzola from comment #5) > So, this bug requests are: > > - --quiet and --verbose should be mutually exclusive done todo: > - log/errors to stderr, output/results to stdout (bug #956518) > - use different log files for each execution avoiding to clean the same log > at start of every application run > - support -y, --assumeyes (like yum) to answer yes to questions or -u, > --unattended (like engine-cleanup) avoiding to ask Continue / Confirm > questions. > > correct?
I'm not sure I'll have enough time for fixing this for 3.3.0.
(In reply to Sandro Bonazzola from comment #6) > (In reply to Sandro Bonazzola from comment #5) > > So, this bug requests are: > > > > - --quiet and --verbose should be mutually exclusive > done > > todo: > > - log/errors to stderr, output/results to stdout (bug #956518) done > > - use different log files for each execution avoiding to clean the same log > > at start of every application run done todo: > > - support -y, --assumeyes (like yum) to answer yes to questions or -u, > > --unattended (like engine-cleanup) avoiding to ask Continue / Confirm > > questions. > > > > correct?
Should we close this? I didn't see any request for this other than this one.
(In reply to Yaniv Dary from comment #9) > Should we close this? > I didn't see any request for this other than this one. Ok, let's close this.