Bug 488603

Description of problem:

When adding steps to a "script" for a kickstart, I left the "scripting language" empty, as the tooltip said it would use the install-time shell if I left it blank.  I then attempted to do a kickstart and received an error message that no argument was given to interpreter.

/rhn/kickstart/KickstartScriptEdit.do

This is the text on the page:

Examples: '/usr/bin/python' '/usr/bin/perl'.
Tip: Leave this field blank to use the install-time shell as language for your post script.

Version-Release number of selected component (if applicable):
Satellite-5.3.0-RHEL5-re20090227.1-i386-embedded-oracle.iso

How reproducible:
Always

Steps to Reproduce:
1. Create kickstart
2. Add a post script to run in chroot
3. Add some steps and leave "scripting language" blank
4. Look at the generated kickstart file
  
Actual results:
Near the end of the kickstart file you will see the steps you added, look at the "%post --interpreter" line.  There is no program specified for the interpreter.  



Expected results:
%post --interpreter /bin/bash
or
%post --interpreter /bin/sh



Additional info:

This is the script I'm running for my test.

%post --interpreter /bin/bash
mkdir /tmp/centos5-tools-channel
cd /tmp/centos5-tools-channel
wget -r -l 1 -nd http://rlx-3-22.rhndev.redhat.com/pub/centos5-tools-channel
rpm -Uvh *.rpm
rhnreg_ks --serverUrl=http://rlx-3-22.rhndev.redhat.com/XMLRPC --activationkey=1-centos5-key --force