pve-cluster: dont pretend to be a time-sync provider

time-sync.target is a special passive unit, consumers (i.e., units that
intend to say "I want to start after synchronized time has been
established") should only order themselves after it. only providers
(i.e., units that intend to say "I am responsible for synchronizing the
clock") should pull it in via a dependency.

this and 2c7182b76f59b32efaba3135c095b9c722957af1 together also fix #998

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>

diff --git a/debian/pve-cluster.service b/debian/pve-cluster.service
index 9cd1a0e0ec4a610da8e557318d54d934d49ee401..da163e8b1a0b4741eb5565c3a618540ec46834ee 100644 (file)
--- a/debian/pve-cluster.service
+++ b/debian/pve-cluster.service
@@ -2,7 +2,6 @@
 Description=The Proxmox VE cluster filesystem
 ConditionFileIsExecutable=/usr/bin/pmxcfs
 Wants=corosync.service
 Description=The Proxmox VE cluster filesystem
 ConditionFileIsExecutable=/usr/bin/pmxcfs
 Wants=corosync.service

-Wants=time-sync.target

 Wants=rrdcached.service
 Before=corosync.service
 Before=ceph.service
 Wants=rrdcached.service
 Before=corosync.service
 Before=ceph.service