Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Task exported creates a tar.gz file which is then added to foreman-debug via add_file statement, but the contract requires only plain text (log) files to be added. There is additional filtering going on underneath, which fails for tarballs creating an output file in invalid format (broken tar).
We need to change the task export foreman-debug statement to create those files unextracted. They can be added all via
add_files /path/to/foreman-export/directory/*
Everything will be compressed, there is no need to create tarballs or compressed tarballs.
TRIAGE NOTES: We need to backport this to improve debug experience for 6.2.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1274694