Bug 977836 - --ticket-number option ignored
--ticket-number option ignored
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-log-collector (Show other bugs)
All Linux
medium Severity medium
: ---
: 3.3.0
Assigned To: Kiril Nesenko
sefi litmanovich
Depends On:
  Show dependency treegraph
Reported: 2013-06-25 08:55 EDT by Julio Entrena Perez
Modified: 2015-09-22 09 EDT (History)
9 users (show)

See Also:
Fixed In Version: rhevm-log-collector-3.3.0-1.el6ev
Doc Type: Bug Fix
Doc Text:
rhevm-log-collector ignores the "--ticket-number" option, which should create a tarball with a ticket number. This has now been fixed, so specifying --ticket-number option will generate a correct tarball name.
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 11:59:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 408043 None None None Never
oVirt gerrit 18388 None None None Never

  None (edit)
Description Julio Entrena Perez 2013-06-25 08:55:22 EDT
Description of problem:
rhevm-log-collector ignores "--ticket-number=" option.
Resulting tarball filename does not include specified case number.

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

How reproducible:

Steps to Reproduce:
1. Run "rhevm-log-collector --ticket-number=00123456"
2. Observe resulting tarball filename.

Actual results:
Tarball filename does not include specified ticket number:

Expected results:
Tarball filename includes specified ticket number:

Additional info:
# rhevm-log-collector --help | grep ticket
                        ticket number to pass with the sosreport

This is very relevant for customer since they rely on the ticket number being present in the filename for automated uploads of logcollectors to us.
Comment 2 sefi litmanovich 2013-09-23 11:50:14 EDT
Verified on rhevm 3.3 is15.
Comment 3 Charlie 2013-11-27 20:16:37 EST
This bug is currently attached to errata RHBA-2013:15255. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 4 errata-xmlrpc 2014-01-21 11:59:37 EST
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.


Note You need to log in before you can comment on or make changes to this bug.