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

Bug 66509

Summary:	anaconda leaves junk in /var/lib on failed upgrade
Product:	[Retired] Red Hat Linux	Reporter:	John Reiser <jreiser>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-06-12 03:24:16 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 John Reiser 2002-06-11 16:18:16 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.19-6.2.16-KRUD-perfctr2.3.6
i586)

Description of problem:
If an upgrade install (for example, 7.2==>7.3) fails because of
fatal error (media, disk space, EPERM in rpm), then anaconda
leaves a junk directory /var/lib/anaconda-rebuilddbNNNNNNNNNN
which can contain 25MB or more of space.  Either this directory
should be removed automatically, or anaconda should give a
message about it.  [If an upgrade fails once, then chances are
it will fail a couple more times before succeeding, and
losing 25MB of disk space each time can cause a failure itself!]

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


How reproducible:
Always

Steps to Reproduce:
1. /usr/bin/chattr +i /bin/cp   # make immutable some file that will be upgraded
2. Attempt to upgrade; it will fail due to EPERM in rpm
3. Reboot, and look in /var/lib/anaconda*
	

Actual Results:  $ du -s /var/lib/anaconda*
24940
$ 


Expected Results:  Either: no junk in /var/lib; or, a message about it.

Additional info:

Comment 1 Michael Fulbright 2002-06-12 03:24:10 UTC

Assigning to an engineer.

Comment 2 Jeremy Katz 2002-07-02 05:35:51 UTC

We don't do rebuilds in the general case anymore, so this isn't a problem with
our current codebase.