Bug 64740

Summary:	failed install leaves rpm database screwed
Product:	[Retired] Red Hat Linux	Reporter:	Neal D. Becker <nbecker>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED NOTABUG	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	athlon
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-05-10 15:43:54 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 Neal D. Becker 2002-05-10 11:54:28 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311

Description of problem:
I just tried to upgrade 7.2->7.2.  The process failed reading the 3rd cdrom. 
Problem is, the rpm  database was not updated.  I tried querying
rpm -q to check the versions of many packages, and they all still say older
versions, even though I can independently verify that many were updated.

Problem is, I don't see any way to recover from this.  Although anaconda is able
to do an update and resolve dependencies, I don't know any way for me to insert,
say, a good cdrom3 and get rpm to update the stuff I missed.


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


How reproducible:
Didn't try

Steps to Reproduce:
1. update with a bad cdrom?
2.
3.
	

Additional info:

Comment 1 Jeremy Katz 2002-05-10 15:46:35 UTC

That's because we are working in a lookaside database in /var/lib/rpm.rebuilddb
-- if you move that to be /var/lib/rpm, instead, you get the new database.