Bug 2062356 - rebase chrony to 4.2
Summary: rebase chrony to 4.2
Alias: None
Deadline: 2022-08-01
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: chrony
Version: 8.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: Ondrej Mejzlik
Šárka Jana
Depends On: 2064790
TreeView+ depends on / blocked
Reported: 2022-03-09 15:54 UTC by Miroslav Lichvar
Modified: 2022-11-08 12:50 UTC (History)
1 user (show)

Fixed In Version: chrony-4.2-1.el8
Doc Type: Enhancement
Doc Text:
.`chrony` rebased to version 4.2 The `chrony` suite has been updated to version 4.2. Notable enhancements over version 4.1 include: * The server interleaved mode has been improved to be more reliable and support multiple clients behind a single address translator (Network Address Translation - NAT). * Experimental support for the Network Time Protocol Version 4 (NTPv4) extension field has been added to improve time synchronization stability and precision of estimated errors. You can enable this field, which extends the capabilities of the protocol NTPv4, by using the `extfield F323` option. * Experimental support for NTP forwarding over the Precision Time Protocol (PTP) has been added to enable full hardware timestamping on Network Interface Cards (NIC) that have timestamping limited to PTP packets. You can enable NTP over PTP by using the `ptpport 319` directive.
Clone Of:
Last Closed: 2022-11-08 10:54:48 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-115045 0 None None None 2022-03-09 16:00:25 UTC
Red Hat Product Errata RHBA-2022:7784 0 None None None 2022-11-08 10:54:54 UTC

Description Miroslav Lichvar 2022-03-09 15:54:49 UTC
Description of problem:
This is a request to rebase chrony to the latest upstream release, currently 4.2.

It has a number of improvements and also some bug fixes:

Comment 12 errata-xmlrpc 2022-11-08 10:54:48 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.


Note You need to log in before you can comment on or make changes to this bug.