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.

Bug 1482565

Summary:	chrony rebase to 3.2
Product:	Red Hat Enterprise Linux 7	Reporter:	Miroslav Lichvar <mlichvar>
Component:	chrony	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED ERRATA	QA Contact:	Andrej Dzilský <adzilsky>
Severity:	medium	Docs Contact:	Lenka Špačková <lkuprova>
Priority:	high
Version:	7.4	CC:	adzilsky, bwelterl, kenneth, mlichvar, psklenar, salmy, thozza
Target Milestone:	rc	Keywords:	Rebase
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	chrony-3.2-1.el7	Doc Type:	Release Note
Doc Text:	_chrony_ rebased to version 3.2 The _chrony_ packages have been upgraded to upstream version 3.2, which provides a number of bug fixes and enhancements over the previous version. Notable enhancements include: * Support for hardware timestamping with bonding, bridging, and other logical interfaces that aggregate ethernet interfaces * Support for transmit-only hardware timestamping with network cards that can timestamp only received Precision Time Protocol (PTP) packets but not Network Time Protocol (NTP) packets * Improved stability of synchronization with hardware timestamping and interleaved modes * An improved "leapsectz" option to automatically set the offset of the system clock between International Atomic Time (TAI) and Coordinated Universal Time (UTC)	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 12:06:26 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:
Bug Depends On:
Bug Blocks:	1465928

Description Miroslav Lichvar 2017-08-17 15:07:25 UTC

Description of problem:
This a request to rebase chrony to 3.2. It includes a number of bug fixes and improvements related to accuracy with HW timestamping and/or interleaved mode. A new option allows unidirectional HW timestamping on network cards that don't support HW RX timestamping of NTP packets. It can also set the TAI-UTC offset of the system clock from tzdata.

Upstream changelog: https://git.tuxfamily.org/chrony/chrony.git/tree/NEWS

Comment 8 Andrej Dzilský 2018-02-08 17:18:10 UTC

Seems we have no reggressions. Verified.

Comment 11 errata-xmlrpc 2018-04-10 12:06:26 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, 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-2018:0753