Bug 1452873
Summary: | The timezone validity filter in anaconda rejects valid timezones that RHEL6 accepted | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Frank Hirtz <fhirtz> | |
Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | |
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | |
Severity: | medium | Docs Contact: | Petr Bokoc <pbokoc> | |
Priority: | medium | |||
Version: | 7.3 | CC: | cww, jstodola, pbokoc, pfrankli, pkotvan, rvykydal, sbueno | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | anaconda-21.48.22.123-1 | Doc Type: | Bug Fix | |
Doc Text: |
Installer now accepts additional time zone definitions in Kickstart files
Starting with Red Hat Enterprise Linux 7.0, *Anaconda* switched to a different, more restrictive method of validating time zone selections. This caused some time zone definitions, such as `Japan`, to be no longer valid despite being acceptable in previous versions, and legacy Kickstart files with these definitions had to be updated or they would default to the `Americas/New_York` time zone.
The list of valid time zones was previously taken from `pytz.common_timezones` in the `pytz` Python library. This update changes the validation settings for the "timezone" Kickstart command to use `pytz.all_timezones`, which is a superset of the `common_timezones` list and which allows significantly more time zones to be specified. This change ensures that old Kickstart files made for Red Hat Enterprise Linux 6 still specify valid time zones.
Note that this change only applies to the "timezone" Kickstart command. The time zone selection in the graphical and text-based interactive interfaces remains unchanged. Existing Kickstart files for Red Hat Enterprise Linux 7 that had valid time zone selections do not require any updates.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1525556 2186608 (view as bug list) | Environment: | ||
Last Closed: | 2018-04-10 08:45:01 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: | ||||
Bug Blocks: | 1420851, 1478303, 2186608 |
Description
Frank Hirtz
2017-05-19 20:00:05 UTC
I understand that the behavior is consistent with the current kickstart documentation: <snip> timezone (required) Sets the system time zone to timezone. To view a list of available time zones, use the timedatectl list-timezones command. </snip> [root@testhost ~]# timedatectl list-timezones | grep 'Japan\|Asia/Tokyo' Asia/Tokyo </snip> ...but it would make carrying forward previous kickstarts simpler and less error-prone if we allow the "historic" timezones to remain as valid options (even if not documented ones). I was able to reproduce this issue on RHEL-7.3 and verify it on RHEL-7.5-20171130.0 with anaconda-21.48.22.128-1.el7. Thanks. Looks good to me, thank you. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0671 |