Bug 76460 - Kickstart install with bad package tracebacks
Summary: Kickstart install with bad package tracebacks
Status: CLOSED DUPLICATE of bug 61903
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 8.0
Hardware: i386 Linux
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-22 01:48 UTC by Chris Adams
Modified: 2007-04-18 16:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 18:50:01 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)
anaconda traceback (69.70 KB, text/plain)
2002-10-22 01:49 UTC, Chris Adams 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Chris Adams 2002-10-22 01:48:20 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
While building a new ks.cfg for 8.0 (starting with one for 7.3), I got a
traceback from anaconda.  I accidentally left "rpm-perl" in the %packages
section.  After anaconda read package information, it crashed and gave a traceback.

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:
1.Build a kickstart file
2.Add a package to the %packages section that doesn't exist in RHL 8.0
3.Install
	

Actual Results:  anaconda tracebacked

Expected Results:  Error message about unknown package

Additional info:
Comment 1 Chris Adams 2002-10-22 01:49:02 UTC 
Created attachment 81464 [details]
anaconda traceback
Comment 2 Jeremy Katz 2003-01-03 06:03:26 UTC 

*** This bug has been marked as a duplicate of 61903 ***
Comment 3 Red Hat Bugzilla 2006-02-21 18:50:01 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.