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): rhevm-log-collector-3.2.2-3.el6ev How reproducible: Always. 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: sosreport-LogCollector-20130625135145.tar.xz Expected results: Tarball filename includes specified ticket number: sosreport-LogCollector-00123456-20130625135145.tar.xz Additional info: # rhevm-log-collector --help | grep ticket --ticket-number=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.
Verified on rhevm 3.3 is15. rhevm-log-collector-3.3.0-1.el6ev
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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHBA-2014-0039.html