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 574049 - error: rpmdb open failed
Summary: error: rpmdb open failed
Keywords:
Status: CLOSED DUPLICATE of bug 471717
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard: anaconda_trace_hash:dae3ffe3d836cfa45...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-16 13:39 UTC by Vladimir Benes
Modified: 2010-08-18 06:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-16 14:19:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (379.16 KB, text/plain)
2010-03-16 13:39 UTC, Vladimir Benes
no flags Details
Attached traceback automatically from anaconda. (143.30 KB, text/plain)
2010-04-23 22:34 UTC, Gordan Bobic
no flags Details
Attached traceback automatically from anaconda. (231.13 KB, text/plain)
2010-05-03 02:24 UTC, Ray Evans
no flags Details
Attached traceback automatically from anaconda. (223.35 KB, text/plain)
2010-05-03 02:27 UTC, Ray Evans
no flags Details
Attached traceback automatically from anaconda. (764.07 KB, text/plain)
2010-05-15 14:32 UTC, Joshua Rosen
no flags Details
Attached traceback automatically from anaconda. (464.21 KB, text/plain)
2010-06-19 21:33 UTC, Alexey Torkhov
no flags Details
Attached traceback automatically from anaconda. (439.94 KB, text/plain)
2010-07-26 19:04 UTC, Jiri Popelka
no flags Details
Attached traceback automatically from anaconda. (296.98 KB, text/plain)
2010-08-18 06:44 UTC, Alexey Kuznetsov
no flags Details

Description Vladimir Benes 2010-03-16 13:39:24 UTC
The following was filed automatically by anaconda:
anaconda 13.21.16 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.6/site-packages/yum/config.py", line 939, in _getsysver
    idx = ts.dbMatch('provides', distroverpkg)
  File "/usr/lib/python2.6/site-packages/yum/config.py", line 832, in readStartupConfig
    startupconf.releasever = _getsysver(startupconf.installroot, startupconf.distroverpkg)
  File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 251, in _getConfig
    startupconf = config.readStartupConfig(fn, root)
  File "/usr/lib/anaconda/yuminstall.py", line 650, in doConfigSetup
    YumSorter._getConfig(self)
  File "/usr/lib/anaconda/yuminstall.py", line 352, in setup
    self.doConfigSetup(root=self.anaconda.rootPath)
  File "/usr/lib/anaconda/yuminstall.py", line 1138, in doBackendSetup
    self.ayum.setup()
  File "/usr/lib/anaconda/backend.py", line 286, in doBackendSetup
    if anaconda.backend.doBackendSetup(anaconda) == DISPATCH_BACK:
  File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/gui.py", line 1308, in nextClicked
    self.anaconda.dispatch.gotoNext()
error: rpmdb open failed

Comment 1 Vladimir Benes 2010-03-16 13:39:29 UTC
Created attachment 400463 [details]
Attached traceback automatically from anaconda.

Comment 2 RHEL Program Management 2010-03-16 13:55:19 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Chris Lumens 2010-03-16 14:19:33 UTC

*** This bug has been marked as a duplicate of bug 471717 ***

Comment 5 Gordan Bobic 2010-04-23 22:34:26 UTC
Created attachment 408751 [details]
Attached traceback automatically from anaconda.

Comment 6 Ray Evans 2010-05-03 02:24:26 UTC
Created attachment 410887 [details]
Attached traceback automatically from anaconda.

Comment 7 Ray Evans 2010-05-03 02:27:46 UTC
Created attachment 410888 [details]
Attached traceback automatically from anaconda.

Comment 8 Joshua Rosen 2010-05-15 14:32:10 UTC
Created attachment 414254 [details]
Attached traceback automatically from anaconda.

Comment 9 Alexey Torkhov 2010-06-19 21:33:52 UTC
Created attachment 425386 [details]
Attached traceback automatically from anaconda.

Comment 10 Jiri Popelka 2010-07-26 19:04:17 UTC
Created attachment 434506 [details]
Attached traceback automatically from anaconda.

Comment 11 Alexey Kuznetsov 2010-08-18 06:44:38 UTC
Created an attachment (id=439307)
Attached traceback automatically from anaconda.

Comment 12 Alexey Kuznetsov 2010-08-18 06:51:11 UTC
this bug trigged by installing f13 on existing f13 installation. to fix it, remove existing /var folder with rpm db.


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