Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 620208 - anaconda 13.42 exception report during upgrade to F13
anaconda 13.42 exception report during upgrade to F13
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity urgent
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-01 10:46 EDT by udo
Modified: 2010-08-01 12:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-01 12:21:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
the exception log (955.72 KB, application/octet-stream)
2010-08-01 10:46 EDT, udo
no flags Details

  None (edit)
Description udo 2010-08-01 10:46:20 EDT
Created attachment 435873 [details]
the exception log

Description of problem:
anaconda 13.42 exception report during upgrade to F13

Version-Release number of selected component (if applicable):
preupgrade-1.1.7-1.fc12.noarch ?

How reproducible:
Install F9 or 10 or so and upgrade to 11 and 12.
Then decide to use preupgrade to upgrade to F13.

Steps to Reproduce:
1. run preupgrade
2. have it download and prepare
3. boot into grub Upgrade menu choice
Actual results:
See attachment

Expected results:
Flawless install

Additional info:
It appears I cannot currently upgrade my systems this way.
Comment 1 udo 2010-08-01 10:48:54 EDT
IndexError: list index out of range

pkgtup: ('kernel', 'x86_64', '0', '', '162.fc12')


[udo@surfplank2 ~]$ rpm -qa|grep kernel
[udo@surfplank2 ~]$ 

It tries to upgrade a non existent package!
How did it get into that?
How do we fix this?
Comment 2 udo 2010-08-01 12:21:17 EDT

rpm db rebuild
yum clean all
and the error does not appear again.
Other issue is in other bug.

Note You need to log in before you can comment on or make changes to this bug.