OCP Version at Install Time: 4.9 Platform: AzureStack, Azure Architecture: x86_64 What are you trying to do? What is your use case? configure Chrony as documented https://docs.microsoft.com/en-us/azure/virtual-machines/linux/time-sync What happened? What went wrong or what did you expect? We need to define through butane machineconfig - the udev rule to create /dev/ptp_hyperv (https://bugzilla.redhat.com/show_bug.cgi?id=1991834) - the proper chrony configuration using /dev/ptp_hyperv and makestep I expect it to work outside the box without any configuration needed. What are the steps to reproduce your issue? Please try to reduce these steps to something that can be reproduced with a single RHCOS node. - boot a rhcos VM on AzureStack - chronyc tracking: shows NTP being used instead of the hardware clock. (side note: there is no documentation on how to upgrade a "single RHCOS node") Implemented on FCOS through https://github.com/coreos/fedora-coreos-config/pull/1355 https://github.com/coreos/fedora-coreos-config/pull/1390
The fix for this in RHCOS 4.11 landed as part of https://github.com/openshift/os/commit/f21cc4b8d4e61c9b92c8f77bf2e0284fb3991c4d Moving to MODIFIED
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069