Bug 768081

Summary: KeyError: 3073
Product: [Fedora] Fedora Reporter: Przemek Klosowski <przemek>
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: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:440b2f8e758a6ae8e3169588c430f5f3fd6bbed8dfd2b744bfd94723a79e7ca3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-09 21:35: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:
Attachments:
Description Flags
File: anaconda-tb-rarhaK none

Description Przemek Klosowski 2011-12-15 17:27:28 UTC
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-7.fc16.i686
product:        Fedora
reason:         KeyError: 3073
time:           Thu Dec 15 12:26:13 2011
version:        16

anaconda-tb-rarhaK: Binary file, 687314 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 16.25 exception report
:Traceback (most recent call first):
:  File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1062, in _run
:    log.error("%s: %s" %(probTypes[ty], descr))
:  File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1021, in run
:    if self._run(instLog, cb, intf) == DISPATCH_BACK:
:  File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1640, in doInstall
:    rc = self.ayum.run(self.instLog, cb, anaconda.intf)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/backend.py", line 205, in doInstall
:    return anaconda.backend.doInstall(anaconda)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward
:    self.dispatch()
:  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked
:    self.anaconda.dispatch.go_forward()
:  File "/usr/lib/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
:    self.intf.icw.nextClicked()
:  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback
:    self.currentWindow.renderCallback()
:KeyError: 3073

Comment 1 Przemek Klosowski 2011-12-15 17:27:35 UTC
Created attachment 547391 [details]
File: anaconda-tb-rarhaK

Comment 2 Chris Lumens 2011-12-15 18:01:09 UTC
There's a lot of really strange warning messages in your log files relating to packages duplicating each other, and an error about not enough space in /boot.  What did you originally have installed on this system and what steps did you take before doing an install?  Did you have a yum transaction that failed for some reason?  Do you have a large number of kernel packages installed?

Comment 3 Przemek Klosowski 2011-12-16 14:36:49 UTC
This is a sad story of an upgrade gone bad. Basically, I had to restart an upgrade, which resulted in a lot of duplicated packages and wasted diskspace. I think the immediate cause was lack of disk space on /boot, but the root cause was a problem with the choice of upgrade packages on Fedora mirrors, as explained below.

I was doing an netinstall upgrade from FC15 to FC16. Midway through the process, I got an error that package 'vte' can't be found: the problem was installation was looking for vte-0.28.2-1 but the currently available package is vte-0.28.2-2 . Anaconda was trying and failing to get the -1 RPM, and the install GUI threw a message about a missing or corrupt RPM, requiring aborting the install. The only two options were Retry and Reboot.

I couldn't think of a way to fake it by slipping the -2 RPM by either renaming to -1 and moving it into RPM staging area, or by installing it by hand (RPM database was locked by Anaconda). I had to reboot, and install the -2 package by hand, and restarting the install, with the result that I had a ton of duplicated packages because the install failed to clean the FC15 packages (I did package-cleanup, see below).

After fixing the 'vte' problem, I ran into two more issues like that: gtk2-devel-docs wanted 2.24.8-2 but the mirrors had 2.24.7-2; also, same problem with kernel-doc (the upgrade process wanted 3.1.5-1 but mirrors have none).

Unfortunately, anaconda doesn't handle these things well--there's no option to skip the package in question. I appreciate that it's not always possible if there are dependencies, but the alternative is a destructive installation abort (the error message essentially says if you reboot you have to reinstall).

I persisted in continuing the installation past those three aborts and the anaconda crash reported here, and got a system with 2213 FC15 and 2399 FC16 packages. I think I resolved the issue by running 'package-cleanup  --cleandupes', although I still have a bunch of pre-FC16 packages.

Comment 4 Chris Lumens 2012-02-09 21:35:06 UTC

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