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 1938016 - [RFE] support for timesync_max_distance to configure maxdistance/maxdist parameter
Summary: [RFE] support for timesync_max_distance to configure maxdistance/maxdist para...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.5
Assignee: Rich Megginson
QA Contact: David Jež
Jaroslav Klech
URL:
Whiteboard: role:timesync
Depends On: 1937938
Blocks: 1938020
TreeView+ depends on / blocked
 
Reported: 2021-03-11 22:40 UTC by Rich Megginson
Modified: 2021-11-09 20:30 UTC (History)
6 users (show)

Fixed In Version: rhel-system-roles-1.1.0-1.el8
Doc Type: Enhancement
Doc Text:
.Users can configure the maximum root distance using the `timesync_max_distance` parameter With this update, the `timesync` RHEL System Role is able to configure the `tos maxdist` of `ntpd` and the `maxdistance` parameter of the `chronyd` service using the new `timesync_max_distance` parameter. The `timesync_max_distance` parameter configures the maximum root distance to accept measurements from Network Time Protocol (NTP) servers. The default value is 0, which keeps the provider-specific defaults.
Clone Of:
: 1938020 (view as bug list)
Environment:
Last Closed: 2021-11-09 17:44:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles timesync pull 89 0 None closed Add option to configure max distance 2021-03-11 22:40:29 UTC
Red Hat Product Errata RHBA-2021:4159 0 None None None 2021-11-09 17:45:14 UTC

Description Rich Megginson 2021-03-11 22:40:29 UTC
Description of problem:
Add ability to configure the ntp `tos maxdist` and the chrony `maxdistance` parameters.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 9 Rich Megginson 2021-04-02 00:02:23 UTC
The test coverage is tests/tests_default_vars.yml

Comment 26 errata-xmlrpc 2021-11-09 17:44:47 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 (rhel-system-roles 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-2021:4159


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