In the next 30th of June time a leap second is a second which is added to Coordinated Universal Time (UTC) in order to synchronize atomic clocks with astronomical time to within 0.9 seconds.
– The last leap second update happened on June 30th 2012 @ 23:59:60 UTC.
– The next leap second update is due June 30th 2015 @ 23:59:60 UTC.
This UTC time change, can and will have a impact in most of our systems(most of the systems have a bug regarding this issue)
So prepare you systems for this change. Or check if they are properly configure for this bug.
In most of the systems we just need to do some changes in your NTP servers.
I will just add a list of some of the systems that you may have in your Virtual Infrastructures that could be impacted with this issue. Will add the proper solutions(or the list for different devices) provided be support.
Follow the link bug search and choose your products
NetApp*: NetApp systems will not be impacted by this bug, but they need to time needs to be proper configured, that your systems are safe. Check NetApp link support for the “how to”
*This support require that you have a support account.
Some of the solution provided is just a workaround, disable NTP servers before the leap second, and then enable again after the lead second occur. This workaround will work for most of the systems, but not so easy to manage with hundred, or thousands of devices.
Hope this can help you how to fix(or reconfigure your systems) and/or bypass this issue in 30th June.
Note: Share this article, if you think is worth sharing.