Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Upstream makes retroactive changes in zone abbreviations, despite it was promised that the new scheme will be applied only to new zones and zone transfers.
Due to rebasing tzdata, this affects *existing* installations, but I believe this is the kind of change that should NOT be done in .z stream, such changes in behaviour should be done only between major RHEL versions.
Version-Release number of selected component (if applicable):
2016g (and maybe older)
How reproducible:
always
Steps to Reproduce:
1. TZ=Asia/Vladivostok date -d "2003-08-03 22:43:22 UTC"
Actual results:
Mon Aug 4 09:43:22 +11 2003
Expected results:
Mon Aug 4 09:43:22 VLAST 2003
Additional info:
In this particular example, the change is very unfortunate - as it was already pointed on the upstream mailinglist (where the new system received significant backlash but was forced by "who codes decides" anyways), Russia uses numbered zones, so ordinary user (not following upstream development) has about zero chance to understand that "+11" does NOT mean "Moscow + 11" in this case.