Bug 2133754

Summary:	Rebase chrony to 4.3
Product:	Red Hat Enterprise Linux 9	Reporter:	Miroslav Lichvar <mlichvar>
Component:	chrony	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED ERRATA	QA Contact:	Ondrej Mejzlik <omejzlik>
Severity:	medium	Docs Contact:	Šárka Jana <sjanderk>
Priority:	medium
Version:	9.1	Keywords:	Rebase, Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	chrony-4.3-1.el9	Doc Type:	Enhancement
Doc Text:	.`chrony` rebased to version 4.3 The `chrony` suite has been updated to version 4.3. Notable enhancements over version 4.2 include: * Added long-term quantile-based filtering of Network Time Protocol (NTP) measurements. You can enable this feature by adding the `maxdelayquant` option to the `pool`, `server`, or `peer` directive. * Added the selection log to provide more information about `chronyd` selection of sources. You can enable the selection log by adding the `selection` option to the `log` directive. * Improved synchronization stability when using the hardware timestamping and Pulse-Per-Second Hardware Clock (PHC) reference clocks. * Added support for the system clock stabilization using a free-running stable clock, for example, Temperature Compensated Crystal Oscillator (TCXO), Oven-Controlled Crystal Oscillator (OCXO), or an atomic clock. * Increased the maximum polling rate to 128 messages per second.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 08:16:03 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:
Embargoed:

Description Miroslav Lichvar 2022-10-11 09:56:04 UTC

Description of problem:
This is a request to rebase chrony to 4.3. The main improvements are improved timekeeping stability with hardware clocks and/or hardware timestamping, and a new log for source selection.

https://chrony.tuxfamily.org/news.html#_31_aug_2022_chrony_4_3_released

Comment 9 errata-xmlrpc 2023-05-09 08:16:03 UTC

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 (chrony bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:2482