Bug 154024 - Kickstart Errors out on Red Hat EL 3 U4
Summary: Kickstart Errors out on Red Hat EL 3 U4
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 3.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-06 16:35 UTC by Jonathon Smith
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-21 21:08:27 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)
Anacdump for DL360 (47.23 KB, text/plain)
2005-04-06 16:35 UTC, Jonathon Smith
no flags Details

Description Jonathon Smith 2005-04-06 16:35:29 UTC
Created attachment 112763 [details]
Anacdump for DL360

Comment 1 Jonathon Smith 2005-04-06 16:35:29 UTC
Description of problem: I can not determine where this kickstart script is 
erroring out. I have used the same kickstart script on other systems and had 
no problems. The current hardware is a DL360 G4


Version-Release number of selected component (if applicable):
Red Hat Enterprise 3 U4

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Jeremy Katz 2005-04-12 16:04:14 UTC
What type of install is this?  A CD install?  

Comment 3 Jeremy Katz 2005-09-21 21:08:27 UTC
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.


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