Description of problem: running sosreport on a stripped-down minimal installation without bzip2 produces an empty tar.bz2 file Version-Release number of selected component (if applicable): sos-1.7-9.16.el5_3.5 How reproducible: 100% reproducible Steps to Reproduce: 1. Install a system with minimum package, excluding bzip2 2. run sosreport Actual results: The tar file in /temp is empty Expected results: The tar file is not empty Additional info: This is because the result is packed using "tar -jcf ..." (packageResults() in lib/sos/policyredhat.py) but neither tar not bzip2 are listed in the requirements The spec file should list: Requires: libxml2-python Requires: tar, bzip2
~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Sos archives its findings in a tar.bz2 file. However, neither tar nor bzip2 were listed as requirements in the sos package. Therefore, on minimal installations that included neither of these tools, sos would produce an empty tar.bz2 file. Sos now requires both these tools, which enable it to create its report.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1418.html