Bug 2127473

Summary:	[RHEL-9] Tokyo/Japan timezone is not set by default after Japanese is selected in the language selection
Product:	Red Hat Enterprise Linux 9	Reporter:	Jan Stodola <jstodola>
Component:	anaconda	Assignee:	Vladimír Slávik <vslavik>
Status:	VERIFIED ---	QA Contact:	Release Test Team <release-test-team>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	jkonecny, kfujii, mmatsuya, sbarcomb, sdubewar, vslavik
Target Milestone:	rc	Keywords:	TestCaseNeeded, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http//
Whiteboard:
Fixed In Version:	anaconda-34.25.3.4-1.el9	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1657646	Environment:
Last Closed:		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 Jan Stodola 2022-09-16 13:37:01 UTC

Description of problem:
When Japanese is selected on the first language screen, New York timezone is selected in the Time & Date spoke.
Tokyo/Japan should be selected by default.

Version-Release number of selected component (if applicable):
RHEL-9.1

How reproducible:
Always

Steps to Reproduce:
1. Run installation in graphical mode.
2. Select Japanese on the first language selection screen.
3. Check the selected timezone in the Time & Date spoke.

Actual results:
New York timezone selected.

Expected results:
Tokyo/Japan selected.

Comment 4 Vladimír Slávik 2023-05-18 12:59:33 UTC

Pull request: https://github.com/rhinstaller/anaconda/pull/4771

Comment 14 Jan Stodola 2023-06-23 08:23:04 UTC

Tested with anaconda-34.25.3.4-1.el9 and no problem was found:

* If geolocation succeeds, language and timezone is set automatically.
* If geolocation succeeds and language is changed on the first screen, timezone is kept unchanged - it means the timezone provided by geolocation is used.
* If geolocation fails or is disabled by inst.geoloc=0, English/New York timezone is pre-selected by default. Changing language also changes the timezone. This is what has changed comparing to RHEL-9.2.

Also tested other scenarios, like setting language/timezone via kickstart, setting language on the kernel cmdline or in text mode. No regression in behavior was found comparing to RHEL-9.2.

What took a slightly longer was a use case when networking could not be brought up automatically (no DHCP on the network), but this delay is present even with anaconda-34.25.3.3-1.el9, so it's not related to this change.

Marking as Verified:Tested.

Comment 17 Jan Stodola 2023-06-26 10:40:33 UTC

Checked that anaconda-34.25.3.4-1.el9 is in nightly compose RHEL-9.3.0-20230626.34

Moving to VERIFIED