Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

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.

Created redmine issue http://projects.theforeman.org/issues/17749 from this bug

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.