Kickstart installs fail around the time they mount the install media if lang is set to something other than en_US - the main example I tried was en_GB but others failed too. A python/anaconda traceback is given, en_GB is not a valid key - I think this is at line 221 in todo.py self.abbrevMap[value] = key However I'm not certain of that exact location.
The installer uses the file /usr/lib/anaconda/lang-table to get the mappings for languages. The version of this file shipped with 6.2 does not appear to contain some languages, so this is why you are having the problem you are. This has been forwards to a developer for further consideration.
this is still open using the pinstripe public beta .... using lang en_GB in the ks file as the language causes an anaconda traceback ...
en_GB isn't a supported language. Read /etc/lang-table for a list, or see documentation which also has a list. Matt
this also fails for ru_RU ...
New valid language codes (from the pinstripe documentation) are: cs_CZ, en_US, fr_FR, de_DE, hu_HU, is_IS, id_ID, it_IT, ja_JP.ujis, no_NO, pl_PL, ro_RO, sk_SK, sl_SI, es_ES, ru_RU.KOI8-R, uk_UA
So I can not kickstart en_UK machines without post-install fixups? That's no good. Oh, I can't even *install* en_UK machines, kickstart or no - they always end up en_US. I think that a second language selection screen is needed, along with some autodetection from the timezone and keyboard type selected. At the very least, the "Which language should be used for the install process" message should be changed to explain that the language will also apply to the installed system.
This problem appears to be fixed in the latest internal trees. Kickstart now works properly for non-us languages.