Bug 98622 - RH9 network install crashes
Summary: RH9 network install crashes
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 9
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-05 19:03 UTC by Need Real Name
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-14 16:22:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2003-07-05 19:03:34 UTC
Description of problem:FTP-style network install on LAN results
in python2.2: rpmte.c:518 rpmteColorDS: Assertion 'ix < Count' failed.
This is after FS formatting while lokong at RPMs on CD#1.
Version-Release number of selected component (if applicable):

How reproducible: completely reporoducible - even with different
choices up to time of error (package selection, disk layout)

Steps to Reproduce:
1.boot pc from floppy, use FTP install, use driver floppy for NIC
2.configure 192.168 network and specify FTP server
3.disk layout, s/w set (tried both workstation or desktop)
Actual results:
install exited abnormally -- received signal 6.  Alternate VT says finally
"* moving (1) to step installpackages"
Expected results: install should proceed through package installation

Additional info:

Comment 1 Michael Fulbright 2003-07-11 15:42:07 UTC
How did you create the file layout on the ftp server which is to act as the
installation source? It looks like a data corruption error.  FTP installs are
known to work.

Comment 2 Need Real Name 2003-07-12 16:53:48 UTC
data corruption confirmed - thanks
description at http://www.notatla.demon.co.uk/MISC/netinstall_prob.txt

Comment 3 Michael Fulbright 2003-07-14 16:22:23 UTC
I'm glad to hear you were able to resolve the problem.

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