FailedQA in ovirt-engine-3.5.0-0.0.master.20140605145557.git3ddd2de.el6.noarch (alpha2).

Substitution of the $UILanguage$ variable with the GUI's UI Language value doesn't work (due to a case-sensitive typo in SysprepHandler.java - $UiLanguage$ vs $UILanguage$).

@Shahar,
also variable for system setup UI language is replaced with GUI's Input Locale value, i.e.,

  sysPrepContent = replace(sysPrepContent, "$SetupUiLanguageUiLanguage$", inputLocale);

Is this correct, shouldn't there be used the UI Language value?

> Is this correct, shouldn't there be used the UI Language value?
Correct,
I will send a patch to fix it.

Verified - https://tcms.engineering.redhat.com/run/163770/

Original request was:

3. What is the nature and description of the request?
customer want to set locale, language and keyboard settings for sysprep operation per vm. They wish to be able to modify the languages defined within the following section of sysprep.xml per vm:

...
   <SetupUILanguage>
      <UILanguage>en-US</UILanguage>
   </SetupUILanguage>
   <InputLocale>en-US</InputLocale>
   <UILanguage>en-US</UILanguage>
   <SystemLocale>en-US</SystemLocale>
   <UserLocale>en-US</UserLocale>
...



4. Why does the customer need this? (List the business requirements here)
This feature is needed because all VMs will NOT be connected to an AD and so the default values for locale language and keyboard should be settable in the sysprep stage.

5. How would the customer like to achieve this? (List the functional requirements here)
These settings should be available in the GUI like the timezone settings currently are.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html