Repository navigation
Conversation
Contributor
Author
|
Regarding migration, what would be the better way to run It could be run:
|
semarie
force-pushed
the
dev/srt/master/chrony-wait
branch
from
November 2, 2026 14:07
6a461ff to
56d931a
Compare
Contributor
Author
|
Last push:
|
`xapi.service` already follows the consumer side of the `time-sync.target` contract in systemd.special(7): services that need a synced clock order themselves `After=time-sync.target` without pulling it in. Pulling the target in is the provider's job, here chrony-wait. The gap is that chrony-wait isn't tied to chronyd: it should run if and only if chronyd does. The commit makes xapi to ship drop-in for chronyd in the xapi package. The `chrony-wait.service` itself should be left not enabled. - `host-installer` should stop enabling chrony-wait at install time - `xsconsole` should stop managing chrony-wait (it is stopped when disabling NTP) - for migration, `systemctl disable chrony-wait.service` should be run Fixes: xapi-project#7363 Signed-off-by: Sebastien Rodot <sebastien.rodot@vates.tech>
semarie
force-pushed
the
dev/srt/master/chrony-wait
branch
from
November 2, 2026 14:24
56d931a to
db0099d
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
xapi.servicealready follows the consumer side of thetime-sync.targetcontract in systemd.special(7): services that need a synced clock order themselvesAfter=time-sync.targetwithout pulling it in. Pulling the target in is the provider's job, here chrony-wait. The gap is that chrony-wait isn't tied to chronyd: it should run if and only if chronyd does.The commit makes xapi to ship drop-in for chronyd in the xapi package.
The
chrony-wait.serviceitself should be left not enabled.host-installershould stop enabling chrony-wait at install timexsconsoleshould stop managing chrony-wait (it is stopped when disabling NTP)systemctl disable chrony-wait.serviceshould be runFixes: #7363