Bug 1155140

Summary:	DST not taken into account on dates after 2038
Product:	Red Hat Enterprise Linux 5	Reporter:	Lukáš Zachar <lzachar>
Component:	glibc	Assignee:	Carlos O'Donell <codonell>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-tools-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.11	CC:	ashankar, fweimer, mcermak, mnewsome, pfrankli, spoyarek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-14 11:29:32 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:

Description Lukáš Zachar 2014-10-21 12:40:34 UTC

Description of problem:

Epoch time is wrong when the date is after year 2038 and DST should be applied.
But it is not and time without DST is returned.

Version-Release number of selected component (if applicable):
glibc-2.5-123

How reproducible:
always

Steps to Reproduce:
1. TZ=Europe/London date +%s -d '2038-05-05'
2. TZ=UTC date +%s -d '2038-05-05'
3.

Actual results:
2156630400 for both cases

Expected results:
2156626800 for London
2156630400 for UTC 

Additional info:

Comment 3 RHEL Program Management 2014-10-25 15:13:07 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 Carlos O'Donell 2014-10-29 17:55:04 UTC

This looks like it might be a tzdata bug. I'm going to ask our tzdata expert to look at this and see if there might be a forthcoming fix for this. The application of DST is based entirely on the timezone data files.