andykimpe / rpms / 389-ds-base

Forked from rpms/389-ds-base 5 months ago
Clone

Blame SOURCES/0006-Issue-49062-Reset-agmt-update-staus-and-total-init

74ca47
From 310b8f8b3c59423b9dfa3a6ea30f4a719f342fc9 Mon Sep 17 00:00:00 2001
74ca47
From: Mark Reynolds <mreynolds@redhat.com>
74ca47
Date: Wed, 1 Mar 2017 10:56:40 -0500
74ca47
Subject: [PATCH] Issue 49062 - Reset agmt update staus and total init
74ca47
74ca47
Description:  Make sure we always reset the agmt status after doing a reinit
74ca47
74ca47
https://pagure.io/389-ds-base/issue/49062
74ca47
74ca47
Reviewed by: tbordaz & nhosoi(Thanks!!)
74ca47
---
74ca47
 ldap/servers/plugins/replication/repl5_tot_protocol.c | 1 +
74ca47
 1 file changed, 1 insertion(+)
74ca47
74ca47
diff --git a/ldap/servers/plugins/replication/repl5_tot_protocol.c b/ldap/servers/plugins/replication/repl5_tot_protocol.c
74ca47
index 57d9de2..45a084a 100644
74ca47
--- a/ldap/servers/plugins/replication/repl5_tot_protocol.c
74ca47
+++ b/ldap/servers/plugins/replication/repl5_tot_protocol.c
74ca47
@@ -591,6 +591,7 @@ retry:
74ca47
 		                 "\"%s\". Sent %lu entries.\n",
74ca47
 		                 agmt_get_long_name(prp->agmt), cb_data.num_entries);
74ca47
 		agmt_set_last_init_status(prp->agmt, 0, 0, 0, "Total update succeeded");
74ca47
+		agmt_set_last_update_status(prp->agmt, 0, 0, NULL);
74ca47
 	}
74ca47
 
74ca47
 done:
74ca47
-- 
74ca47
2.9.3
74ca47