Bug 473159

Summary:	update F9 -> F10 fails
Product:	[Fedora] Fedora	Reporter:	e.mergl
Component:	rpm	Assignee:	Panu Matilainen <pmatilai>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10	CC:	ffesti, jnovy, pmatilai
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:	2009-01-31 10:02:00 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 e.mergl 2008-11-26 20:39:58 UTC

Description of problem:

I tried to update my F9 installation to F10. On the screen saying "Preparing transaction from installation source..." suddenly the background was flooded with error messages like this:

1594 Header V3 DSA signature: BAD, key ID 4f2abfd2
error: rpmdbNextIterator: skipping h#

The progress bar stayed at 30%. After 30 minutes I rebooted the PC.
Fortunately the old F9 installation was still usable.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Chris Lumens 2008-12-02 14:55:10 UTC

This sounds like potential media corruption to me.  Can you attach /tmp/anaconda.log and /tmp/syslog to this bug report?  On the off hand that it's actually an RPM bug (see the error message in the initial comment), I'm also reassigning to RPM.

Comment 2 e.mergl 2008-12-03 20:25:32 UTC

sorry, but I can't provide a logfile, because I did a fresh installation afterwards. Because this fresh installation succeeded I don't think the reason was a media corruption.

Comment 3 Panu Matilainen 2008-12-04 21:03:34 UTC

> 1594 Header V3 DSA signature: BAD, key ID 4f2abfd2
> error: rpmdbNextIterator: skipping h#

This is rpm spotting a damaged header in the rpmdb which as such isn't a bug, if it gets stuck then that might be different. Unless you happen to have a backup of the old rpmdb somewhere, there's too little data here to investigate or do anything about this I'm afraid.

Comment 4 Panu Matilainen 2009-01-31 10:02:00 UTC

Oh well, there's just not enough here to investigate. Please reopen if you encounter it again.