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.
Bug 2133754 - Rebase chrony to 4.3
Summary: Rebase chrony to 4.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: chrony
Version: 9.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: Ondrej Mejzlik
Šárka Jana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-11 09:56 UTC by Miroslav Lichvar
Modified: 2023-05-09 10:18 UTC (History)
0 users

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.
Clone Of:
Environment:
Last Closed: 2023-05-09 08:16:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-136118 0 None None None 2022-10-11 10:03:42 UTC
Red Hat Product Errata RHBA-2023:2482 0 None None None 2023-05-09 08:16:05 UTC

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
Note You need to log in before you can comment on or make changes to this bug.