Bug 896146 - After update 17 to 18 yum update fails with Package tuple not found in rpmdb
Summary: After update 17 to 18 yum update fails with Package tuple not found in rpmdb
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-16 18:01 UTC by dan ginsberg
Modified: 2013-10-09 21:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 21:41:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dan ginsberg 2013-01-16 18:01:42 UTC
Description of problem:

Immediately after upgrading from Fedora 17 to Fedora 18, yum updates fail with the following error message:  "
Error: Package tuple ('gnome-games-help', 'noarch', '1', '3.4.2', '1.fc17') could not be found in rpmdb "


How reproducible:
Update from 17 to 18
sudo su -
yum -y update 


Actual results: Failure:

  [root@localhost ~]# yum -y update --skip-broken
Loaded plugins: langpacks, presto, refresh-packagekit
Error: Package tuple ('gnome-games-help', 'noarch', '1', '3.4.2', '1.fc17') could not be found in rpmdb
[root@localhost ~]# rpm -q gnome-games-help
package gnome-games-help is not installed
[root@localhost ~]# rpm -q yum
yum-3.4.3-47.fc18.noarch



Expected results: yum update works


Additional info:

Comment 1 dan ginsberg 2013-01-16 18:16:30 UTC
was able to fix via

yum clean all


Something ( e.g. fedup? ) ought to have done this as a part of the update process, no?

Comment 2 Joel 2013-01-24 06:31:04 UTC
Had same problem but with a different package:

Error: Package tuple ('libusb1', 'i686', '0', '1.0.9', '0.6.rc1.fc17') could not be found in rpmdb

Also, yum clean all fixed.

Comment 3 David Shea 2013-05-22 21:50:47 UTC
I haven't been able to reproduce this with the versions of fedup and yum currently in the F18 updates repo. After rebooting into the updated system, 'yum update' works fine. Otherwise, this appears to be an issue with yum incorrectly using old data.

Comment 4 Will Woods 2013-10-09 21:41:31 UTC
Assuming this is fixed, then.

If the problem recurs, then yum should probably move/delete invalid metadata during its %post to prevent this from happening.


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