Bug 1025354

Summary:	wrong timezone for Czech
Product:	Red Hat Enterprise Linux 7	Reporter:	Karel Volný <kvolny>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dshea, kvolny, mkolman
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-01 10:15:39 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 Karel Volný 2013-10-31 14:25:02 UTC

Description of problem:
I've tried to install RHEL7 in Czech, but I got Europe/London time zone preselected. It should be Europe/Prague.

Version-Release number of selected component (if applicable):
latest nightly

How reproducible:
always

Steps to Reproduce:
1. run the installer
2. on the language screen, choose Czech
3. on the next screen, look at date time settings

Actual results:
the time zone is Europe/London

Expected results:
the time zone should be Europe/Prague

Additional info:
of course there are some Czech speaking people located in London, but I guess Czech Republic (=> Prague) is the home of vast majority of Czech users :-)

Comment 1 David Shea 2013-10-31 14:32:59 UTC

The default timezone is based on a GeoIP lookup, not language selection. Do you think the geoip data is in error? Can you post the logs from /tmp?

Comment 4 Karel Volný 2013-11-01 14:46:45 UTC

hm, I wonder whether using unrelieable geoip is better choice than also unrealiable bond between language and territory (but at least set by user and not by machine), but I guess this horse is dead already ...

Comment 5 Martin Kolman 2013-11-01 17:23:42 UTC

(In reply to Karel Volný from comment #4)
> hm, I wonder whether using unrelieable geoip is better choice than also
> unrealiable bond between language and territory (but at least set by user
> and not by machine), but I guess this horse is dead already ...
Well, it just preselects the language and the users still has to confirm it. Also it is disabled for automated installs.

Regarding timezones, the territory<->timezone (or actually area/city<->timezone, so that countries like Canada or Russia get correct timezones) works much better.

BTW, regarding the territory<->language mapping, this is handled by the langtable project, which is maintaining (among others) weighted tables of territory<->language mappings. So if GeoIP detects you are in the UK, it gives you English first, followed by the other local languages, like Welsh and Gaelic (but as Anaconda has a translation in only on of them, only language other than English is shown for the UK).

So if you find and weird territory<->language mappings or similar l10n issues, this are valid bugs that should be reported against langtable, so that they can be fixed.