RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 591822 - abrt chooses wrong suffix for sosreport tarball, uses bz2 instead of xz
Summary: abrt chooses wrong suffix for sosreport tarball, uses bz2 instead of xz
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: abrt
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Denys Vlasenko
QA Contact: Michal Nowak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 09:13 UTC by Michal Nowak
Modified: 2013-03-08 02:09 UTC (History)
7 users (show)

Fixed In Version: abrt-1.1.4-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-02 18:47:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch (4.02 KB, patch)
2010-05-25 13:32 UTC, Denys Vlasenko 		no flags Details | Diff
View All

Description Michal Nowak 2010-05-13 09:13:22 UTC 
Description of problem:

This is how SOSreport is started by abrt when I attempted to report via TicketUploader:

sosreport --batch --only=anaconda --only=bootloader --only=devicemapper --only=filesys --only=hardware --only=kernel --only=libraries --only=memory --only=networking --only=nfsserver --only=pam --only=process --only=rpm -k rpm.rpmva=off --only=ssh --only=startup --only=yum

When this is run manually it results in e.g. /tmp/sosreport-dhcp-lab-222-20100513104505-a579.tar.xz (see the XZ suffix). However abrt creates file /tmp/TicketUploader-newticket-20100513081932.tar.gz with following content:

* abrt specific info regarding that crash, and
* sosreport.tar.bz2.

sosreport.tar.bz2 which is itself:

dhcp-lab-222 ~ # file ~newman/Desktop/sosreport.tar.bz2 
/home/newman/Desktop/sosreport.tar.bz2: xz compressed data

Version-Release number of selected component (if applicable):

abrt-1.1.0-1.el6.x86_64
sos-2.1-0.el6.noarch

How reproducible:

always

Steps to Reproduce:
1. Create report via TicketUploader
2. inspect type of tar.bz2 file inside tar.gz one
  
Expected results:

File in *this case* should be named sosreport.tar.xz however one never knows the suffix prio starting sosreport because sosreport chooses compression app depending on what compression apps are present: xz -> bz2.
Comment 1 Denys Vlasenko 2010-05-25 13:32:48 UTC 
Created attachment 416408 [details]
Proposed patch
Comment 2 Denys Vlasenko 2010-05-25 19:08:15 UTC 
Committed the fix to git
Comment 6 releng-rhel@redhat.com 2010-07-02 18:47:38 UTC 
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.