Bug 2233514
| Summary: | Use of "uncommon" TZ names from the KS | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Christophe Besson <cbesson> |
| Component: | anaconda | Assignee: | anaconda-maint |
| Status: | CLOSED MIGRATED | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.8 | CC: | jkonecny, jstodola, prathaku, sbarcomb |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Regression, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-18 17:31:06 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Raising as High as it was working with RHEL 6.10 and not later. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: A customer is wondering why they can't use TZ like ROK, ROC and CET and Brazil/East. Has it been deliberately excluded? Version-Release number of selected component (if applicable): anaconda-33.16.8.9 How reproducible: Always Steps to Reproduce: add into the kickstart: timezone --utc ROK Actual results: WARNING org.fedoraproject.Anaconda.Modules.Timezone:DEBUG:anaconda.modules.timezone.timezone:Timezone is set to ROK. WARNING org.fedoraproject.Anaconda.Modules.Timezone:WARNING:anaconda.modules.timezone.installation:Timezone ROK set in kickstart is not valid, falling back to default (America/New_York). Additional info: pyanaconda/modules/timezone/installation.py: 61 def _correct_timezone(self): 62 """Ensure the timezone is valid.""" 63 if not is_valid_timezone(self._timezone): 64 # this should never happen, but for pity's sake 65 log.warning("Timezone %s set in kickstart is not valid, " 66 "falling back to default (America/New_York).", self._timezone) 67 self._timezone = "America/New_York" pyanaconda/timezone.py: 151 def is_valid_timezone(timezone): 152 """ 153 Check if a given string is an existing timezone. 154 155 :type timezone: str 156 :rtype: bool 157 158 """ 159 160 etc_zones = ["Etc/" + zone for zone in ETC_ZONES] 161 162 return timezone in pytz.common_timezones + etc_zones $ python3 -c "import pytz; print(pytz.common_timezones)" |& grep -c ROK 0 $ python3 -c "import pytz; print(pytz.all_timezones)" |& grep -c ROK 1