RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 803368 - yum update -y on a RHEL6.2 system returns a tuple error
Summary: yum update -y on a RHEL6.2 system returns a tuple error
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-14 15:00 UTC by Harish Pillay
Modified: 2014-01-21 06:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-31 20:11:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Harish Pillay 2012-03-14 15:00:41 UTC
Description of problem:

Running "yum update -y" returns a error saying some package's tuple is not in the rpmdb

Version-Release number of selected component (if applicable):
yum --version
3.2.29
  Installed: rpm-4.8.0-19.el6.x86_64 at 2012-02-03 13:15
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2011-10-04 08:23
  Committed: Panu Matilainen <pmatilai> at 2011-10-04

  Installed: yum-3.2.29-22.el6.noarch at 2012-02-03 13:15
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2011-09-21 14:30
  Committed: James Antill <james.antill> at 2011-09-21

How reproducible:

Run "yum update -y" from a ssh'ed terminal.  Not sure if this error happens the packages are updated from the console (no access to it as the server is in a data center).

Steps to Reproduce:
1. as root, run "yum update -y"
  
Actual results:

[root@rhel6 ~]# yum update -y
Loaded plugins: refresh-packagekit, rhnplugin
Setting up Update Process
Error: Package tuple ('firefox', 'x86_64', '0', '10.0.1', '1.el6_2') could not be found in rpmdb
[root@rhel6 ~]# 

Expected results:

If there was an update, it should have happened.

Comment 2 RHEL Program Management 2012-07-10 06:47:55 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2012-07-11 02:11:35 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 James Antill 2012-07-31 20:11:14 UTC
 I assume this went away on it's own, the above error basically says "yum expected to find something in the rpmdb, but it didn't find it ... so giving up".

 If it was a VM and you can still reproduce it, feel free to reopen and attach all the data about what firefox versions are installed/available (and what the output of "yum check" says).

Comment 5 Harish Pillay 2012-07-31 23:57:42 UTC
Thanks for the update. The problem looks like it went away. Not sure what solved it though.  The yum was not run in a VM.


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