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:
Leap smear (as originally described by Google) is useful when serving time to clients that can't apply leap second slowly by slewing or they don't apply it at at the same time, which means their clocks are not close to each other for a long time after the leap second is applied to UTC. With leap smear the leap second status is suppressed and the time is corrected slowly on the NTP server instead. The clients can track the time easily during whole correction and they stay close together.

In chrony git there is now a smoothtime directive that can be enabled to perform a leap smear. The main difference from the Google implementation is that it's applied after the leap second is inserted to UTC and it can smooth out any offset, not just leap second.

In chrony-2.1-pre1 a leaponly option was added to the smoothtime directive, which allows a synchronized leap smear between multiple servers. It will be included in the chrony package.

The chrony leap smearing feature is explained here:

http://developerblog.redhat.com/2015/06/01/five-different-ways-handle-leap-seconds-ntp/

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