Bug 233233
Summary: | TBc3704fb6 config.py:656:_getsysver:TypeError: rpmdb open failed | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Russ Baker <russ_baker69> | ||||
Component: | pirut | Assignee: | Jeremy Katz <katzj> | ||||
Status: | CLOSED NOTABUG | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | updates | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-03-23 15:44:06 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
Russ Baker
2007-03-21 03:18:34 UTC
Created attachment 150550 [details]
Zipped tar of db files that may be causing problems
Running yum with the -t (tolerate errors) option seemed to get through more than one package before throwing an exception. I think it got about 6 (went from 100 updates remaining to 94), then threw the same type of PANIC messages. Also, the exception occurs immediately after installing a package successfully if I run Add/Remove Software rather than the auto-update selection. Removing a package has the same symptoms. I also ran fsck and badblocks on the disk to make sure I don't have any bad sectors thrown into the mix. This is fixed with newer kernels Newer as in within the last week? I ask because I just downloaded and installed FC6 from the ISO CD images on the mirror sites two weeks ago, so I'm surprised I'm working with an out-of-date kernel... I'm not hugely savvy on the Linux kernel topic in general, so is that normal to have an old buggy kernel downloaded from the site? Is there a specific upgrade process I need to follow that I might have missed? Glad to hear it's a known, fixed bug though. Problem solved! Turns out the problem was that Anaconda installed the i586 kernel the first time around. I tried updating it, but that didn't seem to resolve the issue. So I did a clean re-install and Anaconda selected i686 correctly this time, and everything else seems to have worked out fine. The first thing I did was upgrade the kernel using yum, which had to install multiple packages and didn't have any problem, so I'm pretty sure it was the i586 kernel that caused the grief. |