Bug 1441258

Summary: [RFE] remove dot from the ovirt-log-collector generated file
Product: Red Hat Enterprise Virtualization Manager Reporter: Jaroslav Spanko <jspanko>
Component: ovirt-log-collectorAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED ERRATA QA Contact: David Necpal <dnecpal>
Severity: unspecified Docs Contact:
Priority: low    
Version: 4.1.0CC: lsvaty, lveyde, pbrilla, ylavi
Target Milestone: ovirt-4.2.0Keywords: EasyFix, FutureFeature
Target Release: ---Flags: dnecpal: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-log-collector-4.2.0-1.el7ev Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-15 17:31:24 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:

Description Jaroslav Spanko 2017-04-11 13:52:02 UTC
Description of problem:
Would be possible to remove the dot on the end of tar.xz line ? 
In case of manually copy the line or grab the line with awk the dot is not needed

INFO: Log files have been collected and placed in /tmp/sosreport-LogCollector-20170411153318.tar.xz.

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

How reproducible:
100%

Actual results:
/tmp/sosreport-LogCollector-20170411153318.tar.xz.

Expected results:
/tmp/sosreport-LogCollector-20170411153318.tar.xz

Comment 3 David Necpal 2017-09-04 09:54:18 UTC
Verified on:
ovirt-log-collector-4.2.0-0.0.master.20170825202251.git85a048f.el7.centos.noarch


# ovirt-log-collector 
    .
    .
    .
INFO: Log files have been collected and placed in /tmp/sosreport-LogCollector-20170904115910.tar.xz
    .
    .

Comment 8 errata-xmlrpc 2018-05-15 17:31:24 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-2018:1465

Comment 9 Franta Kust 2019-05-16 13:03:06 UTC
BZ<2>Jira Resync