Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 917490

Summary: An error occurred while setting keyboard layout .
Product: [Retired] oVirt Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2CC: acathrow, chchen, cshao, dyasny, fdeutsch, gouyang, hadong, jboggs, leiwang, mburns, mgoldboi, ovirt-bugs, ovirt-maint, ycui
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-18 10:54:17 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:
Attachments:
Description Flags
attached Screenshot none

Description haiyang,dong 2013-03-04 07:43:57 UTC 
Created attachment 704784 [details]
attached Screenshot

Description of problem:
Install ovirt-node-upstream, enter Keyboard page, then select german keyboard layout.
But an error occurred while setting keyboard layout .(Seen updating keyboard related configuration page1.png)

Although an error occurred while setting keyboard layout, the chosen german keyboard is used correctly.

Version-Release number of selected component (if applicable):
ovirt-node-iso-2.6.1-20120228.fc18.iso        

Steps to Reproduce:
1. Install ovirt-node-upstream, enter Keyboard page.
2. select german keyboard layout.


Actual results:
An error occurred while setting keyboard layout

Expected results:
setting keyboard layout successfully, no error occurred on updating keyboard related configuration page.

Additional info:
----------
Comment 1 Fabian Deutsch 2013-03-04 08:57:35 UTC 
This seems to be a problem of localectl
Comment 2 Fabian Deutsch 2013-03-04 09:21:17 UTC 
(In reply to comment #1)
> This seems to be a problem of localectl

… on Node.
Comment 3 Fabian Deutsch 2013-03-05 09:39:26 UTC 
This looks like an selinux problem as localetl works with setenforce 0
Comment 4 Fabian Deutsch 2013-03-18 10:54:17 UTC 
This error didn't appear on any recent dev build for me.