Bug 520058 - KeyError: 'setuptime'
Summary: KeyError: 'setuptime'
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: ppc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-28 07:45 UTC by Jan Stodola
Modified: 2010-02-25 13:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-28 17:24:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (48.77 KB, text/plain)
2009-08-28 07:45 UTC, Jan Stodola
no flags Details
Attached traceback automatically from anaconda. (150.73 KB, text/plain)
2009-09-18 07:34 UTC, Morgan Olausson
no flags Details
Attached traceback automatically from anaconda. (991.93 KB, text/plain)
2009-11-26 00:25 UTC, Felix Miata
no flags Details
Attached traceback automatically from anaconda. (116.80 KB, text/plain)
2010-02-10 09:22 UTC, Miroslav Vadkerti
no flags Details
Attached traceback automatically from anaconda. (753.30 KB, text/plain)
2010-02-20 16:25 UTC, Clyde E. Kunkel
no flags Details
Attached traceback automatically from anaconda. (200.29 KB, text/plain)
2010-02-25 05:42 UTC, He Rui
no flags Details

Description Jan Stodola 2009-08-28 07:45:22 UTC
The following was filed automatically by anaconda:
anaconda 12.16 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/text.py", line 486, in run
    (file, classNames) = stepToClasses[step]
  File "/usr/bin/anaconda", line 981, in <module>
    anaconda.intf.run(anaconda)
KeyError: 'setuptime'

Comment 1 Jan Stodola 2009-08-28 07:45:27 UTC
Created attachment 359016 [details]
Attached traceback automatically from anaconda.

Comment 2 Jan Stodola 2009-08-28 08:29:13 UTC
The last screen before the anaconda crash is this:

┌────────┤ Error Partitioning ├────────┐
│                                      │
│ Could not find enough free space     │
│ for automatic partitioning, please   │
│ use another partitioning method.     │
│                                      │
│               ┌────┐                 │
│               │ OK │                 │
│               └────┘                 │
│                                      │
│                                      │
└──────────────────────────────────────┘

The same traceback when installing Fedora 11 (anaconda 11.5.0.59)

Comment 3 Jan Stodola 2009-08-28 08:55:18 UTC
During manual installation is no disk found and no disk is found in SMS menu (PowerPC Firmware)

Comment 4 Chris Lumens 2009-08-28 14:42:50 UTC
The real problem here is that we're not finding your hard drives, so of course there's not enough free space to use for automatic partitioning.  However before we solve that problem, let's attempt to solve this KeyError problem.

Does updates=http://clumens.fedorapeople.org/520058.img solve your problem?  You'll probably want to test with the latest anaconda you can find (12.17 is the latest build).

Comment 5 Jan Stodola 2009-08-28 15:36:51 UTC
I was only able to test with anaconda 12.16, but no traceback appears. After this message:

┌──────────────┤ Error Partitioning ├───────────────┐
│                                                   │
│ Could not find enough free space for automatic    │
│ partitioning.  Press 'OK' to exit the installer.  │
│                                                   │
│                      ┌────┐                       │
│                      │ OK │                       │
│                      └────┘                       │
│                                                   │
│                                                   │
└───────────────────────────────────────────────────┘

anaconda rebooted machine as expected.

Comment 6 Chris Lumens 2009-08-28 17:24:50 UTC
Great, thanks for testing.  This will be fixed in the next build of anaconda.

Comment 7 Morgan Olausson 2009-09-18 07:34:20 UTC
Created attachment 361607 [details]
Attached traceback automatically from anaconda.

Comment 8 Felix Miata 2009-11-26 00:25:37 UTC
Created attachment 373883 [details]
Attached traceback automatically from anaconda.

Comment 9 Felix Miata 2009-11-26 00:27:49 UTC
In order to follow up on bug 107748 I attempted to install current rawhide in place of the existing F8 installation on /dev/hda26 via first downloading the installation kernel and initrd to start with grub, but there are no initrd & kernel for Rawhide on the mirrors. So I tried with F12. That started, but refused to start in graphical mode on my rv200 Radeon 7500. I proceeded with text install, and found that after providing requested TZ and password info the partitioner offers only "use entire drive", "replace existing Linux system", & "use free space". Use entire drive is no option, as there are many / partitions with various Linux distros besides DOS, OS/2 & Fedora. Free space is also no option, as there is no unpartitioned space large enough to install anything. So, I chose to replace existing Linux system, and was greeted with "could not allocate requested partitions: not enough free space on disk", which is totally inconsistent with choosing to replace an existing Linux system.

Comment 10 Miroslav Vadkerti 2010-02-10 09:22:05 UTC
Created attachment 389951 [details]
Attached traceback automatically from anaconda.

Comment 11 Clyde E. Kunkel 2010-02-20 16:25:11 UTC
Created attachment 395277 [details]
Attached traceback automatically from anaconda.

Comment 12 Clyde E. Kunkel 2010-02-20 17:26:07 UTC
tried to update a F13RC installation in text mode with 13.28 which seems to have x-server issues with radeon RV630.  Got traceback after selecting update and OK.

Comment 13 He Rui 2010-02-25 05:42:21 UTC
Created attachment 396217 [details]
Attached traceback automatically from anaconda.

Comment 14 James Laska 2010-02-25 13:08:38 UTC
trace hash incorrectly assigned to older bug.  I've moved the  tracehash to a new Fedora 13 bug to track the failures in comment#12 and comment#13.

See bug#568334


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