Bug 46219 - Anaconda exception (fsset.py problem)
Summary: Anaconda exception (fsset.py problem)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
: 47082 47126 49862 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2001-06-27 13:22 UTC by Phil Knirsch
Modified: 2015-03-05 01:09 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2001-07-25 16:14:01 UTC

Attachments (Terms of Use)
Anaconda traceback (1.48 KB, text/plain)
2001-06-27 13:23 UTC, Phil Knirsch
no flags Details

Description Phil Knirsch 2001-06-27 13:22:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.5-9 i686; en-US; rv:0.9.1)

Description of problem:
Anaconda fails at the very end of the installation after the post installation.

Using graphical install with custom setup and manual diskdruid filesystem
setup it installs everything and performs the post installation. Right at
the end of that or right after it (scrollbar is at 100%) i get the attached
anaconda traceback.

I selected grub as bootloader if that helps, but the system didn't come up
afterewards, so i guess it has something to do with that.

Here my partition layout:

Disk /dev/hda: 255 heads, 63 sectors, 3737 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1        66    530113+  82  Linux swap
/dev/hda2            67       328   2104515   83  Linux
/dev/hda3           329       590   2104515   83  Linux
/dev/hda4           591      3737  25278277+  83  Linux

I installed on /dev/hda2.

How reproducible:
Didn't try

Steps to Reproduce:
1.Run installation as described
2.Wait till the very end for the traceback

Actual Results:  System was basically completely installed but didn't boot

Expected Results:  Installation should have finished.

Additional info:

Comment 1 Phil Knirsch 2001-06-27 13:23:01 UTC
Created attachment 21928 [details]
Anaconda traceback

Comment 2 Michael Fulbright 2001-06-27 18:27:50 UTC
Seen this before - katzj is testing with an older python package. Thinking that
recomilation has caused bad code generation.

Comment 3 Brent Nordquist 2001-07-02 17:56:45 UTC
I'm going to tag onto this one; apologies if it's not the same thing.

TUI install of Fairfax beta1 over FTP.

How Reproducible:
Twice in a row, same thing.

At the very end, when the "Performing post install configuration" progress bar
is filled red for the first six spaces, [Exception Occurred]:
Traceback (innermost last)
  File "/usr/bin/anaconda", line 561, in ?
    intf.run(id, dispatch)
  File "/tmp/11581-i386/install//usr/lib/anaconda/text.py", line 386, in run
  File "/tmp/11581-i386/install//usr/lib/anaconda/dispatch.py", line 120, in
  File "/tmp/11581-i386/install//usr/lib/anaconda/dispatch.py", line 185, in
  File "/tmp/11581-i386/install//usr/lib/anaconda/packages.py", line 572, in
  File "/tmp/11581-i386/install//usr/lib/anaconda/packages.py", line 713, in
ValueError: unpack tuple of wrong size

The VT's don't seem to contain anything exceptional.

Comment 4 Brent Nordquist 2001-07-02 20:05:12 UTC
Same result with HTTP install.  See bug 47039 for how I'm configuring TCP/IP,
and bug 46746 for how it autopartitioned (I'm just accepting the default
partitioning now; only steps 1-3 of that bug apply to this bug).

Comment 5 Matt Wilson 2001-07-02 21:31:45 UTC

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

Comment 6 Matt Wilson 2001-07-02 21:32:29 UTC
oops, duped wrong bug

Comment 7 Matt Wilson 2001-07-02 21:49:09 UTC
Brent - this is a different bug, please refile your unpack tuple bug as another bug.

Comment 8 Brent Nordquist 2001-07-03 12:45:33 UTC
Done; see bug 47126.  Sorry for the pollution.  :-)

Comment 9 Jeremy Katz 2001-07-06 04:53:28 UTC
*** Bug 47126 has been marked as a duplicate of this bug. ***

Comment 10 Jeremy Katz 2001-07-10 03:18:55 UTC
*** Bug 47082 has been marked as a duplicate of this bug. ***

Comment 11 Glen Foster 2001-07-13 22:06:22 UTC
This defect considered MUST-FIX for Fairfax gold-release.

Comment 12 Michael Fulbright 2001-07-16 16:19:51 UTC
No real progress on this one yet - msw has enabled some code which should help
isolate it (if it would just happen again).

Comment 13 Brent Nordquist 2001-07-16 16:26:11 UTC
Well, this has a complex history; I tacked onto this bug, was told my problem
was different; created a new bug 47126, which was then marked as a duplicate of

I would be happy to test here, on the hardware where it happened, if you have an
updates disk with the new code.

Comment 14 Matt Wilson 2001-07-24 21:55:36 UTC
*** Bug 49862 has been marked as a duplicate of this bug. ***

Comment 15 Michael Fulbright 2001-07-25 16:13:57 UTC
*** Bug 49862 has been marked as a duplicate of this bug. ***

Comment 16 Matt Wilson 2001-08-09 18:41:51 UTC
fixed a double free in the rpm python binding that was causing this.

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