Bug 1205212

Summary:	fedup initramfs doesn't respect users locale
Product:	[Fedora] Fedora	Reporter:	Christian Stadelmann <fedora>
Component:	fedup-dracut	Assignee:	Will Woods <wwoods>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	awilliam, fedora, tflink, wwoods
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:	2015-04-07 19:41: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:

Description Christian Stadelmann 2015-03-24 12:56:08 UTC

When trying to fedup from F21 to F22 I ran into this problem:
On F21 I set a custom keyboard layout. After rebooting into fedup-initramfs the keyboard layout was set to default en_US layout.

Version-Release number of selected component (if applicable):
fedup 0.9.1 from F21, run today to fedup to F22

Comment 1 Will Woods 2015-03-24 16:04:55 UTC

How did you set the custom keyboard layout? What file(s) were changed?

Comment 2 Christian Stadelmann 2015-03-25 16:39:07 UTC

I don't remember how I set the keyboard layout in F21. It includes using localectl (as root) and setting input sources in gnome-control-center. The system-wide default keyboard layout was my custom layout.
After rebooting from fedup initramfs into the freshly installed F22 it works fine.
In short: the keyboard layout in fedup initramfs is not the same as reported when running localectl on the F21 system as root.

Comment 3 Will Woods 2015-03-31 20:24:36 UTC

Hm. Can you do:
  
  sudo lsinitrd /boot/initramfs-$(uname -r).img /etc/vconsole.conf

and compare that to:

  sudo lsinitrd /boot/initramfs-fedup.img /etc/vconsole.conf

This problem happened in previous versions of fedup, so we started putting your /etc/vconsole.conf into upgrade.img.

If those two files match.. maybe the system has started using a different method for configuring keymaps?

Comment 4 Will Woods 2015-04-07 19:41:17 UTC

This is the same problem as (blocker) bug 1207251, so I'm marking this as a duplicate.

*** This bug has been marked as a duplicate of bug 1207251 ***

Comment 5 Adam Williamson 2015-04-08 14:15:35 UTC

'man vconsole.conf' does note:

"       Depending on the operating system other configuration files might be
       checked for configuration of the virtual console as well, however only
       as fallback."

I think I used to know what those were, but I don't recall any more. I don't think an f21 system is *intended* to set it anywhere else, though.

Comment 6 Christian Stadelmann 2015-04-10 08:05:50 UTC

/etc/vconsole.conf of current F21 installations:
KEYMAP=de-neo
FONT=latarcyrheb-sun16

/etc/vconsole.conf of current F21 initramfs:
KEYMAP=de-neo
FONT=latarcyrheb-sun16

/etc/vconsole.conf of fedup initramfs at the time when `fedup --network 22` finishes and tells me to reboot: does not exist. running `lsinitrd /boot/initramfs-fedup.img /etc/vconsole.conf` with super user privileges does not print anything: no file content and no errors/warnings. It seems like the /etc/vconsole.conf file just does not exist in the fedup intramfs.