Bug 462314 - RPMDB errors
Summary: RPMDB errors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 9
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-15 10:46 UTC by Frank Murphy
Modified: 2009-07-14 14:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-14 14:34:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Yum update error (41.23 KB, text/plain)
2008-09-15 10:46 UTC, Frank Murphy
no flags Details
/var/log/messages/ Yesterday (143.39 KB, application/octet-stream)
2008-09-16 11:01 UTC, Frank Murphy
no flags Details

Description Frank Murphy 2008-09-15 10:46:50 UTC
Created attachment 316723 [details]
Yum update error

Description of problem: cannot yum update, rpm --rebuilddb


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


How reproducible:
Always here on USB-stick install

Steps to Reproduce:
1. Install livecd to USB stick
2. yum update 
3. switch-awy using kvm, swith-back borked.
  
Actual results:
rpmdb borked.

Expected results:
Update sucessful, 


Additional info:
maybe related to: https://bugzilla.redhat.com/show_bug.cgi?id=442250
(usb problems)

Comment 1 Panu Matilainen 2008-09-16 07:41:49 UTC
Does it blow up if you don't switch away with kvm (ie leave out step 3)?

Comment 2 Frank Murphy 2008-09-16 07:59:26 UTC
No, but figured someone needed awareness, just in case it happened to them.

Comment 3 Frank Murphy 2008-09-16 09:54:55 UTC
Addendum: Currently requires full re-install, without switching out, to fix.

Comment 4 Panu Matilainen 2008-09-16 10:41:42 UTC
What does /var/log/messages contain from the time of switching away->switching back? This sounds like the USB subsys gets hosed by the kvm switching (kinda like pulling out and then reinserting the usb stick while rpm is busy writing to it), rpm is certainly not prepared to handle that :)

Comment 5 Frank Murphy 2008-09-16 10:51:06 UTC
That's exactly it, hence the previous bug link. My concern would be for those on full usbhd (updating to). They could get upset if using usb kvm. Doesn't affect F8, only 9 and 10 (so far)

So forearmed is half an octopus.

Comment 6 Frank Murphy 2008-09-16 11:01:53 UTC
Created attachment 316837 [details]
/var/log/messages/ Yesterday

Cannot find a mention of rmp, so give yesterday messages.

Comment 7 Bug Zapper 2009-06-10 02:42:57 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2009-07-14 14:34:23 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.