Bug 1374019 - foreman-debug archive files have confusing extension: .gz.txt
Summary: foreman-debug archive files have confusing extension: .gz.txt
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Debug
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
low
medium vote
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-07 17:16 UTC by Mike McCune
Modified: 2019-09-26 18:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-14 17:26:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17749 0 None None None 2016-12-19 19:00:36 UTC

Description Mike McCune 2016-09-07 17:16:02 UTC 
Certain log files are archived during a foreman-debug run end up as raw txt files in the debug collection but are named:

<filename>.gz.txt

this .gz.txt is confusing to the user as it is hard to determine without actually examining the file .. is it TXT or a gzip archive?

If we are uncompressing these we should name them .txt and drop the '.gz'. If we leave them as archives, drop the .txt
Comment 1 jcallaha 2016-09-09 15:22:37 UTC 
I'd recommend just stripping the .gz since having easily readable text files is much more user friendly than having to unpack anything you want to look at.
Comment 3 Lukas Zapletal 2016-09-22 11:02:15 UTC 
This will create unnecessary complexity into the code, we need to handle special cases (which are in real use, e.g. somelog.gz.1, somelog.gz.2). I like to preserve the original name without any changes.
Comment 4 Zach Huntington-Meath 2016-12-19 18:55:24 UTC 
Created redmine issue http://projects.theforeman.org/issues/17749 from this bug
Comment 6 Bryan Kearney 2017-03-14 17:26:57 UTC 
An upstream issue has been opened for this. When this is fixed, the next version of satellite will contain the fix. We will no longer be tracking this downstream. If you feel this was closed in error, please feel free to re-open with additional information.
Note You need to log in before you can comment on or make changes to this bug.