From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0) Description of problem: Within our facility, we are using a general ks.cfg to install machines. This general ks.cfg uses ondisk within the partition section to create filesystems. We create /boot, swap, and / on the primary drive (/dev/sda) and then create a /vol2 on /dev/sdb. If the machine does not have a /dev/sdb, then the kickstart installation aborts. It would be great if the installation continued and posted a message to one of the log files informing us of the error. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Obtain machine with only a single drive 2. Create a ks.cfg that attempts to create a partition/filesystem on a secondary non-existent drive. 3. Install using the ks.cfg from step and watch the failure. Additional info:
Changing component to anaconda since this seems related to kickstart and not the kickstart configuration tool.
Will address as time allows -- in general, kickstart assumes that your kickstart config is appropriate for the machine being installed on.
We give a slightly better exception now. Still need to catch and provide user-friendly error messages some day, though.