Description of problem: The output lists information that is not necessary but deletes the necessary information about the name and size of the file. Version-Release number of selected component (if applicable): ovirt-log-collector-4.1.3 How reproducible: Always Steps to Reproduce: 1.ovirt-log-collector --quiet 2. 3. Actual results: [root@dn-0 tmp]# ovirt-log-collector --quiet This command will collect system configuration and diagnostic information from this system. The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to skip): Creating compressed archive... Expected results: [root@dn-0 tmp]# ovirt-log-collector --quiet Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to skip): Additional info:
Closing as not a bug. The warning exposed is meant to avoid to generate huge reports which takes hours to complete.
(In reply to Sandro Bonazzola from comment #1) > Closing as not a bug. > The warning exposed is meant to avoid to generate huge reports which takes > hours to complete. Which part is notifying admin about fact it can be a huge report lasting hours? """ This command will collect system configuration and diagnostic information from this system. The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. """ Unfortunately, I do see an issue here, if we decided we want some kind of verbosity during --quite parameter: 1. Agree with reporter, all info should be hidden except asking for password 2. Not sure where this verbose mode is written to, but at least it should be written to stderr 3. If we are indeed writing something out to stdout we should consider at least adding name and path to the archive created, that seems like the most relevant info. Can you reconsider?
Reopening as per comment #2
PR: https://github.com/oVirt/ovirt-log-collector/pull/2
(In reply to Douglas Schilling Landgraf from comment #4) > PR: https://github.com/oVirt/ovirt-log-collector/pull/2 Please push to gerrit.ovirt.org; github is backup only.
Verified on version ovirt-log-collector-4.2.4-1.el7ev.noarch [root@example]# ovirt-log-collector --quiet Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to skip): [root@example]#
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.