Bug 1746444

Summary: rhv-log-collector-analyzer version flag is not shown on help and exists printing random string
Product: Red Hat Enterprise Virtualization Manager Reporter: Guilherme Santos <gdeolive>
Component: rhv-log-collector-analyzerAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED ERRATA QA Contact: Guilherme Santos <gdeolive>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.6CC: mavital, pelauter
Target Milestone: ovirt-4.3.7Keywords: FieldEngineering, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 10:36:34 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 Guilherme Santos 2019-08-28 13:29:33 UTC
Description of problem:
When running rhv-log-collector-analyzer --version, it prints out a random string ("- (git)") and not the version. Also the --version flag it's not specified neither on man nor help

Version-Release number of selected component (if applicable):
0.2.10-0

How reproducible:
100%

Steps to Reproduce:
1. Run rhv-log-collector-analyzer --version
2.
3.

Actual results:
stdout = "- (git)"

Expected results:
stdout = "0.2.10-0"

Additional info:
--version it's no specified on man nor help

Comment 2 Guilherme Santos 2019-11-04 15:31:10 UTC
Verified on:
rhv-log-collector-analyzer-0.2.12-0.el7ev.noarch (rhv-log-collector-analyzer-0.2.12-0.el7ev.noarch)

Steps:
# rhv-log-collector-analyzer --version
# man rhv-log-collector-analyzer

Results:
stdout for --version showing the version and flag (--version) now specified on man

Comment 4 errata-xmlrpc 2019-12-12 10:36:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4229