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.
Bug 2117174 - DST : postpone the September 2022 time change from 3rd September to 10th September for Chile
Summary: DST : postpone the September 2022 time change from 3rd September to 10th Sep...
Keywords:
Status: CLOSED DUPLICATE of bug 2117032
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tzdata
Version: 8.6
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-10 08:40 UTC by Ravindra Patil
Modified: 2023-07-18 14:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 13:12:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-130804 0 None None None 2022-08-10 08:42:34 UTC

Description Ravindra Patil 2022-08-10 08:40:34 UTC 
Description of problem:

At the governmental level, it has been determined to postpone the September 2022 time change, as a result of the constitutional plebiscite, i.e. it should not change on September 3 from -4 to -3. This change should occur on September 10.

This should not happen:

America/Santiago  Sun Sep  4 03:59:59 2022 UTC = Sat Sep  3 23:59:59 2022 -04 isdst=0 gmtoff=-14400
America/Santiago  Sun Sep  4 04:00:00 2022 UTC = Sun Sep  4 01:00:00 2022 -03 isdst=1 gmtoff=-10800

The Chilean government has finalized that this change should occur on september 10, 2022, so we need the updated tzdata patch.


What is the business impact? Please also provide timeframe information.
High

Where are you experiencing the behavior? What environment?
Production

When does the behavior occur? Frequency? Repeatedly? At certain times?
In this time change


Version-Release number of selected component (if applicable):
tzdata-2022a-1.el8.noarch.rpm

How reproducible:
Update tzdata package for 3rd September DST time changes

Steps to Reproduce:
1. Update tzdata package
2. Wait for time changes to happen


Actual results:
Time would be changed or corrected from from -4 to -3 on 3rd September

Expected results:
Time should changed or corrected from from -4 to -3 on 10th September

Additional info:
The Chilean government has finalized that this change should occur on september 10, 2022.
Comment 1 Juan Gamba 2022-08-10 13:12:03 UTC 

*** This bug has been marked as a duplicate of bug 2117032 ***
Note You need to log in before you can comment on or make changes to this bug.