Bug 1800503

Summary:	In Hammer, it is not possible to set default keyboard layout for a RHEV host
Product:	Red Hat Satellite	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Compute Resources - RHEV	Assignee:	Yifat Makias <ymakias>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	egolov, ehelms, inecas, mshira, orabin, tbrisker, ymakias
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-2.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:00:15 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:
Embargoed:

Description Lukáš Hellebrandt 2020-02-07 09:44:20 UTC

Description of problem:
When adding a RHEV CR in Hammer, it is possible to select default display type but it's not possible to select default keyboard layout (as opposed to WebUI where both is possible).

Version-Release number of selected component (if applicable):
Sat 6.7, new functionality

How reproducible:
Deterministic

Steps to Reproduce:
1. # hammer compute-resource create --help

Actual results:
No info about setting default keyboard layout for RHEV

Expected results:
Info about setting default keyboard layout for RHEV which actually works

Comment 3 Yifat Makias 2020-03-03 15:26:48 UTC

While trying to reproduce this bug I saw that there is a keyboard option when creating a new RHEV compute resource however, there is no such option when creating a host and I think there should be.

Comment 4 Yifat Makias 2020-03-03 15:40:10 UTC

Created redmine issue https://projects.theforeman.org/issues/29254 from this bug

Comment 5 Bryan Kearney 2020-03-04 09:07:12 UTC

Upstream bug assigned to ymakias

Comment 6 Bryan Kearney 2020-03-04 09:07:18 UTC

Upstream bug assigned to ymakias

Comment 7 Bryan Kearney 2020-03-12 16:05:46 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29254 has been resolved.

Comment 8 Lukáš Hellebrandt 2020-06-24 14:08:00 UTC

FailedQA with Sat 6.8 snap 5.0.

While the command help now correctly contains "--keyboard" parameter description, using it has actually no effect:

# hammer compute-resource create --name testv4Hammer8 --provider Ovirt --url https://<RHEV_FQDN>/ovirt-engine/api --user <rhev_login> --password <rhev_password> --datacenter Satellite-Devel --display-type VNC --keyboard fo

=> Results in a CR created with correct display type but keyboard always being "en-us".

Comment 9 Lukáš Hellebrandt 2020-09-24 11:34:35 UTC

Verified with Sat 6.8 snap 17.

# hammer compute-resource create --help | grep layout -A1
 --keyboard-layout KEYBOARD_LAYOUT           For RHEV only
                                             Possible value(s): 'ar', 'de-ch', 'es', 'fo', 'fr-ca', 'hu', 'ja', 'mk', 'no', 'pt-br', 'sv', 'da', 'en-gb', 'et', 'fr', 'fr-ch', 'is', 'lt', 'nl', 'pl', 'ru', 'th', 'de', 'en-us', 'fi', 'fr-be', 'hr', 'it', 'lv', 'nl-be', 'pt', 'sl', 'tr'

# hammer compute-resource create --name rhev2 --provider ovirt --use-v4 yes --url https://<FQDN>/ovirt-engine/api --user <user> --password <password> --datacenter Satellite-Engineering --display-type SPICE --keyboard-layout fr-ca
Compute resource created.

Checked in WebUI that the layout is indeed set to fr-ca.

Additionally, checked that the parameter only accepts acceptable values, the error is:
```
Could not create the compute resource:
  Error: Option '--keyboard-layout': Value must be one of 'ar', 'de-ch', 'es', 'fo', 'fr-ca', 'hu', 'ja', 'mk', 'no', 'pt-br', 'sv', 'da', 'en-gb', 'et', 'fr', 'fr-ch', 'is', 'lt', 'nl', 'pl', 'ru', 'th', 'de', 'en-us', 'fi', 'fr-be', 'hr', 'it', 'lv', 'nl-be', 'pt', 'sl', 'tr'..
```

Comment 12 errata-xmlrpc 2020-10-27 13:00:15 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 (Important: Satellite 6.8 release), 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://access.redhat.com/errata/RHSA-2020:4366