Bug 866204

Summary: error: rpmdb open failed
Product: [Fedora] Fedora Reporter: Keith Bare <fc32004>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, stephent98, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:edb30f20ffa33074d3d6f0220a901a6469321104d68a25a651d1735a3b4059ab
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-15 14:46:19 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:
Attachments:
Description Flags
File: release
none
File: anaconda.log
none
File: type
none
File: ifcfg.log
none
File: storage.log
none
File: version
none
File: environ
none
File: product
none
File: syslog
none
File: install.log
none
File: hashmarkername
none
File: packaging.log
none
File: cmdline_file
none
File: anaconda-tb
none
File: program.log none

Description Keith Bare 2012-10-14 16:33:10 UTC
Description of problem:
I attempted to install F18-TC4 in place of an old F15 installation.  In the custom partitioing screen I selected the preexisting /boot and / partitions and entered those same mount points and hit apply changes.  The F18 tree then showed those partitions inside.  I hit done.  No other changes were made to installer defaults.  Proceeded to the next step.  Screen prompts for a root password, but an error windows pops up not more than 5 seconds into the installation process.

Version-Release number of selected component:
anaconda-18.16

Additional info:
libreport version: 2.0.14
cmdline:        /usr/bin/python  /sbin/anaconda
kernel:         3.6.1-1.fc18.x86_64

description:
:The following was filed automatically by anaconda:
:anaconda 18.16 exception report
:Traceback (most recent call first):
:  File "/usr/lib/python2.7/site-packages/rpmUtils/transaction.py", line 58, in dbMatch
:    mi = self.ts.dbMatch(*args, **kwds)
:  File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 1212, in _get_packages
:    mi = ts.dbMatch(*args, **kwds)
:  File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 1258, in _search
:    for hdr, idx in mi:
:  File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 1193, in searchNames
:    returnList.extend(self._search(name=name))
:  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4480, in install
:    ipkgs = self.rpmdb.searchNames([po.name])
:  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3597, in selectGroup
:    pkg_warning_level='debug2')
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 946, in _selectYumGroup
:    self._yum.selectGroup(groupid, group_package_types=pkg_types)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1053, in _applyYumSelections
:    self._selectYumGroup("core")
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1097, in checkSoftwareSelection
:    self._applyYumSelections()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1176, in preInstall
:    self.checkSoftwareSelection()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 111, in doInstall
:    payload.preInstall(packages=packages, groups=payload.languageGroups(ksdata.lang.lang))
:  File "/usr/lib64/python2.7/threading.py", line 504, in run
:    self.__target(*self.__args, **self.__kwargs)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
:    threading.Thread.run(self, *args, **kwargs)
:error: rpmdb open failed

Comment 1 Keith Bare 2012-10-14 16:33:13 UTC
Created attachment 627017 [details]
File: release

Comment 2 Keith Bare 2012-10-14 16:33:15 UTC
Created attachment 627018 [details]
File: anaconda.log

Comment 3 Keith Bare 2012-10-14 16:33:16 UTC
Created attachment 627019 [details]
File: type

Comment 4 Keith Bare 2012-10-14 16:33:18 UTC
Created attachment 627020 [details]
File: ifcfg.log

Comment 5 Keith Bare 2012-10-14 16:33:20 UTC
Created attachment 627021 [details]
File: storage.log

Comment 6 Keith Bare 2012-10-14 16:33:21 UTC
Created attachment 627022 [details]
File: version

Comment 7 Keith Bare 2012-10-14 16:33:23 UTC
Created attachment 627023 [details]
File: environ

Comment 8 Keith Bare 2012-10-14 16:33:25 UTC
Created attachment 627024 [details]
File: product

Comment 9 Keith Bare 2012-10-14 16:33:28 UTC
Created attachment 627025 [details]
File: syslog

Comment 10 Keith Bare 2012-10-14 16:33:30 UTC
Created attachment 627026 [details]
File: install.log

Comment 11 Keith Bare 2012-10-14 16:33:32 UTC
Created attachment 627027 [details]
File: hashmarkername

Comment 12 Keith Bare 2012-10-14 16:33:34 UTC
Created attachment 627028 [details]
File: packaging.log

Comment 13 Keith Bare 2012-10-14 16:33:36 UTC
Created attachment 627029 [details]
File: cmdline_file

Comment 14 Keith Bare 2012-10-14 16:33:38 UTC
Created attachment 627030 [details]
File: anaconda-tb

Comment 15 Keith Bare 2012-10-14 16:33:40 UTC
Created attachment 627031 [details]
File: program.log

Comment 16 Steve Tyler 2012-10-14 17:47:37 UTC
I'm not sure if this matters, but your hardware clock seems to be way off:

From attached syslog:
16:23:14,042 WARNING chronyd: System clock wrong by 186949800.262671 seconds, adjustment started

Also, sda6 had some filesystem errors:
16:23:18,658 WARNING kernel:[   62.667813] EXT4-fs warning (device sda6): ext4_clear_journal_err:4419: Filesystem error recorded from previous mount: IO failure

Comment 17 Steve Tyler 2012-10-14 19:08:46 UTC
(In reply to comment #16)
...
> Also, sda6 had some filesystem errors:
> 16:23:18,658 WARNING kernel:[   62.667813] EXT4-fs warning (device sda6):
> ext4_clear_journal_err:4419: Filesystem error recorded from previous mount:
> IO failure

That looks like: Bug 839891 - e2fsck leaves ext4 journal unfixed
Bug 839891, Comment 19 says it was fixed in kernel-3.5.3-1.fc17.x86_64, so presumably it is fixed in 3.6.1-1.fc18.x86_64 ...

Comment 18 Chris Lumens 2012-10-15 14:46:19 UTC

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