Bug 589446 - ignoredisk kickstart option now shows error if disk does not exist
Summary: ignoredisk kickstart option now shows error if disk does not exist
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 6.1
Hardware: All Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-06 07:55 UTC by Frido Ferdinand
Modified: 2010-05-06 12:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-06 12:47:02 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)

Description Frido Ferdinand 2010-05-06 07:55:11 UTC
Description of problem:

ignoredisk kickstart option now shows a critical error if a disk does not exist. This is a change from rhel5 where this check did not exist. We're using a kickstart file that is used for many types of hardware, in the ignoredisk we usually put the second disk like /dev/sdb, /dev/cciss/c0d1. Now we have to edit the kickstart if that device does not happen to exist on the target machine.


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

rhel6-beta1

How reproducible:


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


Expected results:


Additional info:

Comment 2 RHEL Product and Program Management 2010-05-06 09:35:49 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Chris Lumens 2010-05-06 12:47:02 UTC
Correct - kickstart is now less forgiving of errors, as a way to help you catch problems before you end up doing things to disks that you didn't want to do.  It's acting more like a real language now and less like an ad-hoc system.


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