Bug 769476

Summary:	glibc update to glibc-2.14.90-25.fc17 makes all times displayed UTC only
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	glibc	Assignee:	Jeff Law <law>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	collura, fweimer, jakub, law, mfranc, schwab, thoger, usdanskys, yaneti
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-24 01:20:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michal Jaegermann 2011-12-20 23:32:20 UTC

Description of problem:

After an update to the last rawhide glibc-2.14.90-25.fc17.x86_64 all times are displayed _only_ like that: "Tue Dec 20 23:19:47 UTC 2011".  After a reboot timestamps in log files also switched from a local time to UTC.  That despite that /etc/localtime exists (and it happens to be the same one as /usr/share/zoneinfo/America/Edmonton and it did not change for a long time).

'strace' on 'date' shows that /etc/localtime is opened for reading but a timezone information is disregarded.  Setting TZ only changes a timezone marker but other than that 'date' and 'date -u' show the same time.

Version-Release number of selected component (if applicable):
glibc-2.14.90-25.fc17.x86_64

How reproducible:
always

Additional info:
More precisely I do not have an absolute evidence that glibc is a culprit and I did not try to revert that update but it is hard to imagine what else on the list of the last batch of updates could have such pervading influence.  I have a feeling that this may be related to a "fix" for bug 767696.

Comment 1 Yanko Kaneti 2011-12-21 11:14:34 UTC

I can confirm that downgrading to the latest one from the F16 testing updates fixes it.

Comment 2 Steven Usdansky 2011-12-21 12:45:18 UTC

Reverting to glibc-2.14.90-23.fc17.x86_64 fixed the problem for me.

Comment 3 Tomas Hoger 2011-12-21 13:36:21 UTC

Looks like we lost this fix with update from master:

http://pkgs.fedoraproject.org/gitweb/?p=glibc.git;a=commitdiff;h=e13f8ca66c97805fb6cea90236334579e9ab1c61

Comment 4 Jeff Law 2011-12-21 17:15:45 UTC

It hadn't been committed to the master when I updated rawhide; I didn't realize it was going to have this impact.  I'll resync shortly to address a few random issues.

Comment 5 Michal Jaegermann 2011-12-24 01:20:05 UTC

With glibc-2.14.90-26.fc17 displayed times look as before (but parts of logs are already in the future :-).