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
Created attachment 513751 [details] Attached traceback automatically from anaconda.
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.
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.
*** Bug 727390 has been marked as a duplicate of this bug. ***
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.
http://clumens.fedorapeople.org/723167.img works for me. (Other issues surface, trying to bz them.)
(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.
(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.
Created attachment 516645 [details] tmp_kernelOops.tar.gz
If there are other errors, let's track those separately.
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
Created attachment 516995 [details] storage.log /tmp/storage.log corresponding to attachment #516994 [details]
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!
*** Bug 729053 has been marked as a duplicate of this bug. ***
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
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).
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
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
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
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.