Bug 1893101

Summary: nl-be keymap should be removed
Product: [oVirt] ovirt-engine Reporter: Jean-Louis Dupond <jean-louis>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.2.6CC: ahadas, bugs
Target Milestone: ovirt-4.4.4   
Target Release: 4.4.4   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-13 16:31:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.