Bug 1953549

Summary: Can't install OS because VConsole can't start - loadkeys: Unable to open file: us: No such file or directory
Product: Red Hat Enterprise Linux 9 Reporter: smitterl
Component: kbdAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Haruda <jharuda>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 9.0CC: david.chang, dhorak, jharuda, virt-qe-z
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kbd-2.4.0-4.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 13:19:09 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:
Bug Depends On: 1950406    
Bug Blocks:    
Attachments:
Description Flags
lpar log
none
vconsole setup service log none

Description smitterl 2021-04-26 11:18:52 UTC 
Description of problem:

VConsole can't be set up because loadkeys provided by kbd returns error, it seems.

This causes dracut to fail to ask for additional kernel parameters and the installation can't continue.


Version-Release number of selected component (if applicable):
kbd-2.4.0-3.el9.s390x

How reproducible:
100%


Steps to Reproduce:
1. Install RHEL 9 in an LPAR using an FTP server[1]
OR partially reproduce:
1'. Install RHEL 9 into a virtual machine with libvirt:
# virt-install --name rhel9 --memory 2048 --vcpus 2 --disk size=10 --location <ftp-installation-tree-url> --nographics --network default --os-variant rhel-unknown

Actual results:
ad 1. systemd-vconsole-setup.service can't start, the installation can't continue.

"
[[0;1;31mFAILED[0m] Failed to start [0;1;39mSetup Virtual Console[0m.

[    5.499889] systemd[1]: systemd-vconsole-setup.service: Main process exited, 

code=exited, status=1/FAILURE

[    5.499994] systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'.
[    5.500109] systemd[1]: Failed to start Setup Virtual Console.
[    5.500135] systemd[1]: Dependency failed for dracut ask for additional cmdline parameters.
[    5.500150] systemd[1]: dracut-cmdline-ask.service: Job dracut-cmdline-ask.se
rvice/start failed with result 'dependency'.
"

ad 1'. systemd-vconsole-setup.service can't start. However, with libvirt the installation continues and shows the anaconda menu, IIUC, because libvirt uses a different console to connect to the installation[2]

Journal:
"
Apr 26 09:45:36 fedora systemd[1]: Starting Setup Virtual Console...
Apr 26 09:45:36 fedora systemd-vconsole-setup[1342]: loadkeys: Unable to open file: us: No such file or directory
Apr 26 09:45:36 fedora systemd-vconsole-setup[1338]: /usr/bin/loadkeys failed with exit status 1.
Apr 26 09:45:36 fedora systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE
Apr 26 09:45:36 fedora systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'.
"

Expected results:


Additional info:


[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_a_standard_rhel_installation/index#installing-in-an-lpar-using-an-ftp-server_installing-in-an-lpar
[2] Instead of sclp line mode as on LPAR:
<console type='pty' tty='/dev/pts/6'>
      <source path='/dev/pts/6'/>
      <target type='sclp' port='0'/>
      <alias name='console0'/>
</console>
[3] This doesn't happen with kbd-2.4.0-2. More specifically, it is reproducible with compose ID RHEL-9.0.0-20210425.3 but not with RHEL-9.0.0-20210419.3. In both composes systemd version is systemd-247.3-2.el9.s390x
[4] I'm trying to install on hardware z15.
Comment 1 smitterl 2021-04-26 11:22:30 UTC 
Created attachment 1775473 [details]
lpar log
Comment 2 smitterl 2021-04-26 11:22:57 UTC 
Created attachment 1775474 [details]
vconsole setup service log
Comment 3 Dan Horák 2021-04-26 15:22:07 UTC 
there is no change between kbd-2.4.0-3.el9 and kbd-2.4.0-2.el9, except -3 went thru the mass rebuild with the new architecture level (-march=z14), so this bug might be a symptom of some deeper problem
Comment 4 smitterl 2021-04-26 16:32:13 UTC 
Thanks @Dan. For now I updated the description to include that I try to install on z15.
Comment 5 Vitezslav Crhonek 2021-04-27 06:40:26 UTC 
(In reply to Dan Horák from comment #3)
> there is no change between kbd-2.4.0-3.el9 and kbd-2.4.0-2.el9, except -3
> went thru the mass rebuild with the new architecture level (-march=z14), so
> this bug might be a symptom of some deeper problem

The rebuild itself is the problem, see bug #1950406. There are keymaps missing in kbd-misc.
Comment 6 Vitezslav Crhonek 2021-05-05 09:17:11 UTC 
Can you please confirm that the issue is fixed with kbd-2.4.0-4.el9?
Comment 7 smitterl 2021-05-05 10:53:09 UTC 
Hi Vitezslav! Yes, this is fixed with kbd-2.4.0-4.el9.

I could install the latest RHEL 9 Beta compose id RHEL-9.0.0-20210504.5 successfully.
Comment 8 Vitezslav Crhonek 2021-05-18 13:19:09 UTC 
Thanks, I'll close the bug then.