On Tue, Dec 5, 2017 at 1:17 PM, Numan Siddique <[email protected]> wrote: > > > On Dec 5, 2017 9:16 PM, "Russell Bryant" <[email protected]> wrote: > > On Mon, Dec 4, 2017 at 9:27 AM, <[email protected]> wrote: >> From: Numan Siddique <[email protected]> >> >> Pacemaker Resource agent periodically calls the OVN OCF's "monitor" action >> periodically to check the status. But the OVN OCF script doesn't add the >> action "monitor" for the role "Master" because of which the pacemaker >> resource agent do not call the "monitor" action at all for the master. >> In case OVN db servers exit for some reason this totally gets undetected >> and one of the standby node is not promoted to master. >> >> This patch adds the monitor action for "Master" role. Also the monitor >> action do not check for the status of the ovn-northd (if manage_northd is >> yes). >> This patch also checks for the status of the ovn-northd in the monitor >> action >> for the "Master" role. If any of the ovsdb-server or ovn-northd is not >> running, >> monitor action will return OCF_NOT_RUNNING and this will cause the >> pacemaker >> to restart the OVN OCF resource. >> >> Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=1512568 >> Signed-off-by: Numan Siddique <[email protected]> >> CC: Russell Bryant <[email protected]> > > Thanks, Numan. I applied v4 to master and branch-2.8. > > > Thanks Russell for the review and applying. Is it possible to apply this to > branch 2.7 as well since we see the issue there.
Backported to branch-2.7 as well. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
