Bug 6547 – text mode boot floppy install barfs on update

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 6547 - text mode boot floppy install barfs on update

Summary:	text mode boot floppy install barfs on update

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Jay Turner
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-10-30 18:29 EDT by trever_adams
Modified:	2015-01-07 18:39 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-08 21:31:08 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description trever_adams 1999-10-30 18:29:01 EDT

This happens with the updated disks pre-October 30th as well
as with those supplied on the cd-rom.

I have three systems, hard drive setup is largely identical,
another which is different.  One of the similar and the
different have cdrom's.  The install from CD (update from
6.0) works wonderfully.  The two that don't have cdroms, I
installed from floppy (image from cd, image from errata,
image from errata with linux updates... all the same).
During the stage where it is getting the packages it chokes
and crashes with a Python, I believe, error.  It is
something like this

name = something[rpm.SOMETHING]

something and SOMETHING were different.  I don't have access
to the machines right now, or I would provide more info.
The caps are as were in the line of code, if I remember
correctly.

Please fix this in your next errata images.

Trever Adams

Comment 1 Jay Turner 1999-11-30 10:42:59 EST

I will need the text of the error message to now what the source of the problem
is.  Please submit that error text and we will replicate here in the lab.

Comment 2 Jay Turner 2000-02-08 21:30:59 EST

I am guessing that when you made the hard drive images for installation, you got
the TRANS.TBL files copied over from the CDROMs and this is causing the
problem.  There is a known problem with the 6.1 installer that causes it to
throw a python excpetion when the installer encountered a non-RPM file.  Check
the RPMS directory and verify that there are no files of this type.  Reopen this
bug if you continue to have problems.

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