systemd: Start OSDs after MONs

Currently, we start/stop OSDs and MONs simultaneously. This may cause
problems especially when we are shutting down the system. Once the mon
goes down it causes a re-election and the MONs can miss the message
from the OSD that is going down.

Resolves: http://tracker.ceph.com/issues/18516

Signed-off-by: Boris Ranto <branto@redhat.com>
(cherry picked from commit 7f4acf45dd0d86e7d9992a8c30e5876fb57b1914)

Conflicts:
	systemd/ceph-osd@.service (jewel does not have 4179aa8d)

diff --git a/systemd/ceph-osd@.service b/systemd/ceph-osd@.service
index bd5a78be84c256b9ef04edc8dff285003dc8c228..ad0c5f8d216e4abdd2a2868e7b00b19008dd9931 100644 (file)
--- a/systemd/ceph-osd@.service
+++ b/systemd/ceph-osd@.service
@@ -1,6 +1,6 @@
 [Unit]
 Description=Ceph object storage daemon
-After=network-online.target local-fs.target time-sync.target
+After=network-online.target local-fs.target time-sync.target ceph-mon.target
 Wants=network-online.target local-fs.target time-sync.target
 PartOf=ceph-osd.target