Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 960846 - Support to configure keyboard Layout for Automated Installation
Support to configure keyboard Layout for Automated Installation
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
6.5
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Ryan Barry
Virtualization Bugs
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-08 02:52 EDT by cshao
Modified: 2014-01-21 14:33 EST (History)
15 users (show)

See Also:
Fixed In Version: ovirt-node-3.0.1-5.el6
Doc Type: Enhancement
Doc Text:
The hypervisor could support 'configure keyboard layout' from the TUI, but it didn't support it for automated installation. This has been changed so the keyboard layout can now be configured during auto installation.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-21 14:33:24 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 18455 None None None Never
Red Hat Product Errata RHBA-2014:0033 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-21 19:14:30 EST

  None (edit)
Description cshao 2013-05-08 02:52:13 EDT
Description of problem:

Currently rhev-h can support configure keyboard layout form TUI, but it doesn't support for Automated installation.

So it would be better if RHEV-H support to configure keyword layout for Automated Installation 

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130501.0.el6_4

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:
RHEV-H only support to configure keyboard layout for TUI.

Expected results:
It would be better if RHEV-H support to configure keyword layout for Automated Installation.

Additional info:
Comment 4 cshao 2013-10-29 00:54:37 EDT
Test version:
rhevh-6.5-20131024.1.0
ovirt-node-3.0.1-6.el6.noarch

The keyboard layout(keyboard=us/de) have beed added into the path.
Auto install with below parameters can successfully.
BOOTIF=eth0 storage_init=/dev/sda keyboard=de(or us) firstboot

After reboot, the defalut keyboard have set to German.
So the bug is fixed, change bug status to VERIFIED.
Comment 6 Cheryn Tan 2013-11-07 19:25:56 EST
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 8 errata-xmlrpc 2014-01-21 14:33:24 EST
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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html

Note You need to log in before you can comment on or make changes to this bug.