Bug 1374019

Summary:	foreman-debug archive files have confusing extension: .gz.txt
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Foreman Debug	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.2.0	CC:	bbuckingham, bkearney, jcallaha, zhunting
Target Milestone:	Unspecified	Keywords:	EasyFix, Triaged
Target Release:	Unused
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:	2017-03-14 17:26:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.