From 8e7eb94645355024a12417aa247fa3eecc586274 Mon Sep 17 00:00:00 2001
From: Kotresh HR <khiremat@redhat.com>
Date: Mon, 1 Oct 2018 04:37:47 -0400
Subject: [PATCH 387/387] georep: Fix config set of monitor status

The backport of [1] introduced config set of monitor
status using new config framework available in
upstream but is not available in downstream. Hence
introduced the issue in downstreamwhere monitor
failed to start workers. Fixed the same and marking
in downstream only.

[1] https://code.engineering.redhat.com/149760


BUG: 1623749
Change-Id: Ia80b66137d0a3b193d178859a5d3c5fca01aa623
Signed-off-by: Kotresh HR <khiremat@redhat.com>
Reviewed-on: https://code.engineering.redhat.com/gerrit/151428
Tested-by: RHGS Build Bot <nigelb@redhat.com>
Reviewed-by: Sunil Kumar Heggodu Gopala Acharya <sheggodu@redhat.com>
---
 geo-replication/syncdaemon/monitor.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/geo-replication/syncdaemon/monitor.py b/geo-replication/syncdaemon/monitor.py
index 3451fe4..1b03d7d 100644
--- a/geo-replication/syncdaemon/monitor.py
+++ b/geo-replication/syncdaemon/monitor.py
@@ -384,7 +384,7 @@ class Monitor(object):
         # It will also cause fd leaks.
 
         self.lock.acquire()
-        set_monitor_status(gconf.get("state-file"), self.ST_STARTED)
+        set_monitor_status(gconf.state_file, self.ST_STARTED)
         self.lock.release()
         for t in ta:
             t.join()
-- 
1.8.3.1