Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 523263

Summary:	sosreport captures the contents of /tftpboot. On a Satellite server that can be about a gig
Product:	Red Hat Enterprise Linux 5	Reporter:	Thomas Cameron <tcameron>
Component:	sos	Assignee:	Adam Stokes <astokes>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.5	CC:	agk, ahecox, azelinka, bmr
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-30 08:08:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Thomas Cameron 2009-09-14 16:20:59 UTC

Description of problem:
Just installed RHN Satellite 5.3 on one of my servers.  As part of the installation, it created install media for all of RHEL 3, 5 and 5, 32- and 64-bit, in /tftpboot.  sosreport includes all of the content in /tftpboot and the sospreport I created went from 5-6 megs to almost a gig.  Perhaps we should no longer include the contents of /tftpboot?

Version-Release number of selected component (if applicable):
sos-1.7-9.27.el5

How reproducible:
Install RHN Satellite 5.3
Run sosreport

Actual results:
sosreport output is about a gigabyte.

Expected results:
sosreport output should be less than 10 megs.

Additional info:

Comment 5 errata-xmlrpc 2010-03-30 08:08:02 UTC

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-2010-0201.html