Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When leap second is inserted to UTC, the system clock is corrected by the kernel by stepping the clock backwards at 0:00:00 UTC. This can be a problem for applications which need the system time to be monotonic or without any jumps.

The development version of chrony now has a new option "leapsecmode" which can be used to select between different leap second handling modes. The clock can be either stepped by the kernel (the default), stepped by chronyd, slowly adjusted by slewing, or the leap second can be ignored and corrected later in normal operation.

When the slewing mode is used, the correction starts at 0:00:00 UTC and is applied at the slewing rate set by the maxslewrate directive. The fixed starting time means that clocks on all NTP clients using the same setting stay together during that correction.

http://git.tuxfamily.org/chrony/chrony.git/commit/?id=f8db83249133127f32281f80a2fc1ce1faaba203

Version-Release number of selected component (if applicable):
chrony-1.29.1

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2241.html