Bug 1893101 - nl-be keymap should be removed
Summary: nl-be keymap should be removed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.2.6
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.4
: 4.4.4
Assignee: Arik
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-30 07:48 UTC by Jean-Louis Dupond
Modified: 2020-12-21 12:38 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.4.4
Clone Of:
Environment:
Last Closed: 2020-11-13 16:31:42 UTC
oVirt Team: Virt
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 111995 0 master MERGED Remove nl-be keymap and add cz from VNC options 2021-02-04 09:06:28 UTC
oVirt gerrit 112098 0 master MERGED core: update existing vms with nl-be keymap to en-us 2021-02-04 09:06:28 UTC

Description Jean-Louis Dupond 2020-10-30 07:48:25 UTC 
Description of problem:
The nl-be keymap was removed from Qemu:
https://github.com/qemu/qemu/commit/b7c9d9f07e08ba3b812eb51f3772664a81afd117#diff-cab969986c6024c7f79510451d47911096f529e2da300ec43c9716e186f78e6a

But you can still choose it in oVirt.


How reproducible:
Edit VM settings
Set keymap to nl-be
-> VM will not boot
2020-10-30T07:26:59.281771Z qemu-kvm: -vnc xxxx:17,password,tls-creds=vnc-tls-creds0: could not read keymap file: 'nl-be'.
Comment 1 RHEL Program Management 2020-10-30 09:52:32 UTC 
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Comment 2 Casper (RHV QE bot) 2020-11-13 16:31:42 UTC 
This bug has a low overall severity and passed automated regreession suite, it is not going to be further verified by QE. If you believe a special care is required feel free to re-open to ON_QA status
Comment 3 Sandro Bonazzola 2020-12-21 12:38:53 UTC 
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.