Bug 1371123

Summary: A positive leap second on 31st December 2016
Product: Red Hat Gluster Storage Reporter: Bipin Kunal <bkunal>
Component: unclassifiedAssignee: Atin Mukherjee <amukherj>
Status: CLOSED NOTABUG QA Contact: Rahul Hinduja <rhinduja>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: amukherj, bkunal, rhs-bugs, sankarshan, smohan, storage-qa-internal, vpakolu
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-15 11:13:46 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:

Description Bipin Kunal 2016-08-29 12:02:43 UTC
Description of problem:

A positive leap second will be introduced on 31st of December, 2016

Version-Release number of selected component (if applicable):
RHEL, any version
tzdata up to 2016f-1

How reproducible:
always

Steps to Reproduce:
1. zdump -v right/America/Los_Angeles | grep Sat.Dec.31.*2016

Actual results:
no output

Expected results:
should output about the leap second insertion

Additional info:
https://datacenter.iers.org/eop/-/somos/5Rgv/latest/16

Comment 4 Bipin Kunal 2016-08-29 12:11:36 UTC
References KCS : https://access.redhat.com/solutions/2441291

Reference RHEL BZ :
   RHEL 7 : BZ #1356098
   RHEL 6 : BZ #1356220

Comment 5 Atin Mukherjee 2016-08-29 13:00:27 UTC
Could you explain why is this BZ related to Gluster and more specifically GlusterD? A more detailed explanation would help us in identifying the scope of this request.

Comment 6 Bipin Kunal 2016-08-29 13:34:48 UTC
This BZ has nothing to do directly with Gluster. As we have RHEL as base, all the product based on RHEL and using tzdata would be affected. 

Mostly we recommend to use NTP server for syncing time and we do not recommend to be dependent on tzdata package so there is very less likely that Glusterfs deployment is vulnerable to this. Fixing the issue on ntp server will fix  issue here as well.

This BZ has been opened in order to track all the effort being taken in order to fix leap second issue.

Comment 7 Bipin Kunal 2016-09-28 07:01:39 UTC
Removed customer case 01710247 as the issue was reported for pure RHEL.