Bug 1555449

Summary: [RFE] Reduce Archive Size by using filters message via flags unclear
Product: [oVirt] ovirt-log-collector Reporter: mlehrer
Component: RFEsAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.4CC: bugs, eheftman, mlehrer
Target Milestone: ovirt-4.3.0Keywords: FutureFeature
Target Release: 4.3.0Flags: rule-engine: ovirt-4.3?
rule-engine: planning_ack?
sbonazzo: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-log-collector-4.3.0_beta1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:46:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mlehrer 2018-03-14 18:01:41 UTC
Description of problem:

The following message after collection is unclear.
"You can use the following filters in the next execution -c, -d, -H to reduce the archive size."

Current wording is confusing as I wasn't sure if it was listing additional compression options or what it meant.
The majority of options for flags listed in help use --WORD and not -letter.
 
I think a few additional words would be helpful.

"You can use the following filters -c, -d, -H in the next execution to limit the number of RHV datacenters, clusters, or hosts that are collected in order to reduce the archive size.  Try ovirt-log-collector -help for additional information."


-=>>ovirt-log-collector --user=admin@internal --no-hypervisors
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.
INFO: Gathering oVirt Engine information...
INFO: Gathering PostgreSQL the oVirt Engine database and log files from localhost...
INFO: Skipping hypervisor collection...
INFO: Creating compressed archive...
INFO: Log files have been collected and placed in /tmp/sosreport-LogCollector-20180314164432.tar.xz
The MD5 for this file is b14dd7b9dfc1195c3574e7fe07b00d49 and its size is 1084.4M
You can use the following filters in the next execution -c, -d, -H to reduce the archive size.



Version-Release number of selected component (if applicable):
ovirt-log-collector-4.2.4-3.el7ev.noarch

How reproducible:
Reproduces

Steps to Reproduce:
1. execute ovirt-log-collector
2. review error message


Actual results:
You can use the following filters in the next execution -c, -d, -H to reduce the archive size.

Expected results:
"You can use the following filters -c, -d, -H in the next execution to limit the number of RHV datacenters, clusters, or hosts that are collected in order to reduce the archive size.  Try ovirt-log-collector -help for additional information."


Additional info:

Perhaps this is very clear to everyone, it wasn't to me and that's why I filed this.

Comment 2 Douglas Schilling Landgraf 2018-10-25 18:35:22 UTC
Sure, anything that improves is welcome. My suggestion is:

  '\nYou can use the following filters -c, -d, -H in the '
  'next execution to limit the number of Datacenters,\n'
  'Clusters or Hosts that are collected in order to '
  'reduce the archive size.'

Comment 3 Sandro Bonazzola 2018-10-31 08:32:47 UTC
@mlehrer is message in comment #2 clear enough for you?

Comment 4 Lucie Leistnerova 2018-12-07 10:26:19 UTC
When the report is > 1000M it shows message from Comment 2.

verified in ovirt-log-collector-4.3.0-0.2.beta1.el7ev.noarch

If you still think that the message is not enough understandable, please reopen this BZ.

Comment 5 Sandro Bonazzola 2019-02-13 07:46:46 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 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.