Hide Forgot
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
References KCS : https://access.redhat.com/solutions/2441291 Reference RHEL BZ : RHEL 7 : BZ #1356098 RHEL 6 : BZ #1356220
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.
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.
Removed customer case 01710247 as the issue was reported for pure RHEL.