Bug 620208 - anaconda 13.42 exception report during upgrade to F13
Summary: anaconda 13.42 exception report during upgrade to F13
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 12
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-01 14:46 UTC by udo
Modified: 2010-08-01 16:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-01 16:21:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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 14:46 UTC, udo
no flags Details

Description udo 2010-08-01 14:46:20 UTC
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 14:48:54 UTC
IndexError: list index out of range

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


???

[udo@surfplank2 ~]$ rpm -qa|grep kernel
abrt-addon-kerneloops-1.1.1-2.fc12.x86_64
kernel-debug-devel-2.6.31.6-145.fc12.x86_64
kernel-firmware-2.6.32.16-141.fc12.noarch
kernel-headers-2.6.32.16-141.fc12.x86_64
[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 16:21:17 UTC
Nevermind

rpm db rebuild
yum clean all
preupgrade
etc
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.