Bug 723167

Summary: error: rpmdb open failed
Product: [Fedora] Fedora Reporter: He Rui <rhe>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: anaconda-maint-list, awilliam, clydekunkel7734, jonathan, satellitgo, twu, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:ba9479b6697549870700c8233c3d0b78b5093452ee918e7b890566dd1b1fd18a AcceptedNTH
Fixed In Version: anaconda-16.14.6-1.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-18 22:25:15 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:
Bug Depends On:    
Bug Blocks: 713563, 713564    
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
rpmdb open failed in 16.13 also
none
tmp_kernelOops.tar.gz
none
anaconda traceback and debug info
none
storage.log none

Description He Rui 2011-07-19 09:56:02 UTC
The following was filed automatically by anaconda:
anaconda 16.12 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1434, in getReleaseString
    mi = ts.dbMatch('provides', 'initscripts')
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1493, in findExistingRootDevices
    (arch, product, version) = getReleaseString(anaconda.rootPath)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/upgrade.py", line 81, in findRootParts
    upgradeany=flags.cmdline.has_key("upgradeany"))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 338, in dispatch
    self.dir = self.steps[self.step].target(self.anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 235, in go_forward
    self.dispatch()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1200, in nextClicked
    self.anaconda.dispatch.go_forward()
error: rpmdb open failed

Comment 1 He Rui 2011-07-19 09:56:07 UTC
Created attachment 513751 [details]
Attached traceback automatically from anaconda.

Comment 2 He Rui 2011-07-19 10:35:54 UTC
It happened every time when I boot pre-alpha installer(http://serverbeach1.fedoraproject.org/pub/alt/stage/20110714/x86_64/iso/) to a virt guest which has an installed system using gpt partition table.

Comment 3 Clyde E. Kunkel 2011-07-22 17:59:01 UTC
Created attachment 514758 [details]
rpmdb open failed in 16.13 also

this is from: Fedora-16-test-20110721-3-x86_64.iso.  Can't get around it.

Comment 4 Chris Lumens 2011-08-02 12:43:04 UTC
*** Bug 727390 has been marked as a duplicate of this bug. ***

Comment 5 Chris Lumens 2011-08-03 14:51:01 UTC
Can you try updates=http://clumens.fedorapeople.org/723167.img against a tree containing anaconda-16.14-1?  This looks pretty stupid, like we're trying to open an rpmdb on systems that won't ever contain one when trying to find an upgrade candidate.

Comment 6 Clyde E. Kunkel 2011-08-03 18:14:16 UTC
http://clumens.fedorapeople.org/723167.img works for me.  (Other issues surface, trying to bz them.)

Comment 7 He Rui 2011-08-04 02:38:10 UTC
(In reply to comment #5)
> Can you try updates=http://clumens.fedorapeople.org/723167.img against a tree
> containing anaconda-16.14-1?  This looks pretty stupid, like we're trying to
> open an rpmdb on systems that won't ever contain one when trying to find an
> upgrade candidate.

I cannot reproduce this issue on anaconda 16.14.

Comment 8 He Rui 2011-08-04 07:49:38 UTC
(In reply to comment #7)
> (In reply to comment #5)
> > Can you try updates=http://clumens.fedorapeople.org/723167.img against a tree
> > containing anaconda-16.14-1?  This looks pretty stupid, like we're trying to
> > open an rpmdb on systems that won't ever contain one when trying to find an
> > upgrade candidate.
> 
> I cannot reproduce this issue on anaconda 16.14.

I can reproduce the issue now when I boot F16-alphaTC1 to a guest which has F-15 installed. By using the updates, this issue didn't happen, but kernel oops happened as well as an error: cannot open Packages database in /mnt/sysimage/var/lib/rpm. Log attached.

Comment 9 He Rui 2011-08-04 07:51:05 UTC
Created attachment 516645 [details]
tmp_kernelOops.tar.gz

Comment 10 Chris Lumens 2011-08-04 14:29:42 UTC
If there are other errors, let's track those separately.

Comment 11 John Reiser 2011-08-06 15:04:22 UTC
Created attachment 516994 [details]
anaconda traceback and debug info

"error: rpmdb open failed"

Installing from DVD (Fedora 16 Alpha RC1) to a machine which has many partitions, including several non-upgradable (FC6, Ubuntu, ...)  I intended to do a fresh install overwriting an existing partition, but never got far enough to make that choice.

anaconda 16.14.2 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1449, in getReleaseString
    mi = ts.dbMatch('provides', 'initscripts')
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1508, in findExistingRootDevices
    (arch, product, version) = getReleaseString(anaconda.rootPath)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/upgrade.py", line 81, in findRootParts
    upgradeany=flags.cmdline.has_key("upgradeany"))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 348, in dispatch
    self.dir = self.steps[self.step].target(self.anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 235, in go_forward
    self.dispatch()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1198, in nextClicked
    self.anaconda.dispatch.go_forward()
error: rpmdb open failed

Comment 12 John Reiser 2011-08-06 15:05:20 UTC
Created attachment 516995 [details]
storage.log

/tmp/storage.log corresponding to attachment #516994 [details]

Comment 13 Adam Williamson 2011-08-08 21:31:35 UTC
Working on the assumption that 729053 is a dupe of this, we accepted the issue as NTH at the QA meeting today, so can we please get a new anaconda 16.14.x build with the fix for this added in? Thanks!

Comment 14 Adam Williamson 2011-08-08 21:32:34 UTC
*** Bug 729053 has been marked as a duplicate of this bug. ***

Comment 15 Fedora Update System 2011-08-09 04:25:38 UTC
anaconda-16.14.3-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/anaconda-16.14.3-1.fc16

Comment 16 Fedora Update System 2011-08-09 06:02:30 UTC
Package anaconda-16.14.3-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-16.14.3-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/anaconda-16.14.3-1.fc16
then log in and leave karma (feedback).

Comment 17 Fedora Update System 2011-08-11 15:49:45 UTC
anaconda-16.14.4-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/anaconda-16.14.4-1.fc16

Comment 18 Fedora Update System 2011-08-15 16:55:30 UTC
anaconda-16.14.5-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/anaconda-16.14.5-1.fc16

Comment 19 Fedora Update System 2011-08-16 20:14:41 UTC
anaconda-16.14.6-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/anaconda-16.14.6-1.fc16

Comment 20 Fedora Update System 2011-08-18 22:24:14 UTC
anaconda-16.14.6-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.