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.
Created attachment 1538990[details]
patch made by git diff
After upgrading my ntp pool server from CentOS 6.10 ntpd to CentOS 7.6 chronyd I noticed that chronyd do not respond to RFC 1059 packets. There was 8.6 % NTPv1 mode 0 requests from all IPv4 NTP pakets in one 100k-packets sample (the IPv6 clients seem to use versions 3 and 4 only).
This is already fixed in the upstream:
https://git.tuxfamily.org/chrony/chrony.git/commit/ntp_core.c?id=fbca570d0b12e47f502a2e4ecc76f1a05d2c2d12
A patched version of chrony 3.2 is already running on my server and it responds to version 1 mode 0 packets with mode 4 (server). Hope the clients are satisfied with mode 4 although this behavior doesn't follow the RFC 1059. Unfortunately I have no such version 1 client to test if it cares about mode 4.
It would be nice to include this fix in current RHEL 7 chrony package.
Thanks.