-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move the call to reload ntp settings to the server only #14208
Conversation
Previously, when the ntp settings were changed every worker would enqueue a message for the server to reload the settings when they went through the Config::Activator. Multiple calls to restart chronyd within a matter of seconds causes systemd to backoff and fail the unit causing chronyd not to run until the appliance is rebooted or it is started manually. This change makes the server reload the ntp settings every time its config is changed, but removes the call to reload from the activator which removes all the calls generated when the workers refresh their settings. This results in just one call to reload the settings when the config is changed rather than tens.
Checked commit carbonin@939524f with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good. Tested this yesterday with @carbonin
Move the call to reload ntp settings to the server only (cherry picked from commit 515b4a0) https://bugzilla.redhat.com/show_bug.cgi?id=1429999
Euwe backport details:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice. I believe set_config is called throughout the UI, although I don't think you have to in the backend. This should be good enough to solve this problem.
Move the call to reload ntp settings to the server only (cherry picked from commit 515b4a0) https://bugzilla.redhat.com/show_bug.cgi?id=1429999
Previously, when the ntp settings were changed every worker would enqueue a message for the server to reload the settings when they went through the Config::Activator.
Multiple calls to restart chronyd within a matter of seconds causes systemd to back off and fail the unit causing chronyd not to run until the appliance is rebooted or it is started manually.
This change makes the server reload the ntp settings every time its config is changed, but removes the call to reload from the activator which removes all the calls generated when the workers refresh their settings. This results in just one call to reload the settings when the config is changed rather than tens.
https://bugzilla.redhat.com/show_bug.cgi?id=1429714