Bug 1057996

Summary: PRD34 - [RFE] RunOnce dialog can not set a vnc keymap itself
Product: Red Hat Enterprise Virtualization Manager Reporter: Itamar Heim <iheim>
Component: RFEsAssignee: Scott Herold <sherold>
Status: CLOSED ERRATA QA Contact: meital avital <mavital>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: acathrow, adahms, dfediuck, ecohen, gklein, iheim, lpeer, mavital, mgoldboi, ofrenkel, sbonazzo, sherold, s.kieske, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: ovirt-3.4.0-beta3 Doc Type: Enhancement
Doc Text:
This update adds the ability to select the VNC keyboard layout to be used by a virtual machine when starting that machine using the Run Once window.
Story Points: ---
Clone Of: 1031040 Environment:
Last Closed: 2014-06-09 15:01:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1031040    
Bug Blocks: 1078909, 1142926    

Description Itamar Heim 2014-01-26 11:41:48 UTC
+++ This bug was initially created as a clone of Bug #1031040 +++

Description of problem:
you can't select another keymap for vnc via runonce

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Select a shutdown vm
2. click "run once"
3. select display options "vnc"

Actual results:
you can just select vnc or spice, but not keyboard layout

Expected results:
you can also specify the keymap

Additional info:
This would be a cool feature.

--- Additional comment from Sandro Bonazzola on 2013-12-23 03:08:09 EST ---

Kobi, can you please add gerrit reference and target release? Thanks!

--- Additional comment from Kobi on 2013-12-23 04:22:01 EST ---

(In reply to Sandro Bonazzola from comment #1)
> Kobi, can you please add gerrit reference and target release? Thanks!

Done, 10x

Comment 2 errata-xmlrpc 2014-06-09 15:01:55 UTC
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.