Bug 655608

Summary: RFE: RHEL6 kickstart fails with unknown command
Product: Red Hat Enterprise Linux 6 Reporter: Marco Bill-Peter <marcobillpeter>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: low    
Version: 6.0CC: mkhusid
Target Milestone: rcKeywords: FutureFeature, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-04 19:15:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 645519    
Attachments:
Description Flags
console screenshot none

Description Marco Bill-Peter 2010-11-21 23:20:01 UTC
Created attachment 461886 [details]
console screenshot

Description of problem:

a kickstart install fails with Unknown Command and states the install exited abnormally due to an old command passed (kickstart file reused)

see screenshot for exact failure

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

6.0 GA
anaconda 13.21.82

How reproducible:

use old commands like langsupport in kick start file and start the install. 

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

see attached screnshot from console

Expected results:

a softer message, like "ignoring unknown command" but proceeding with the install


Additional info:

Comment 2 Chris Lumens 2010-11-22 13:28:46 UTC
This is how kickstart works - you use a command that no longer exists, and kickstart halts with an error message.  It's just like any other language in this respect.  langsupport was deprecated in time for RHEL5 which means you've had a warning getting logged since then.

Comment 6 Chris Lumens 2011-01-06 18:28:01 UTC
It's also worth pointing out that you can use the ksvalidator command in the pykickstart package to check your kickstart config file before running it through anaconda, just to make sure you're not using anything that's invalid.