<div dir="ltr">Hi Numan,<div><br></div><div><br></div><div>Finally figure it out what's wrong when running ovndb-servers ocf in my environment.</div><div><br></div><div>1. There is no default ovnnb and ovnsb running in my environment, I thought it should be started by pacemaker as the usual way other typical resource agent do it.</div><div>when I create the ovndb_servers resource, nothing happened, no operation is executed except monitor, which is really hard to debug for a while.</div><div>In the ovsdb_server_monitor() function, first it will check the status, here, it will be return NOT_RUNNING, then in the ovsdb_server_master_update() function, "CRM_MASTER -D" is being executed, which appears stopped every following action, I am not very clear what work it did.<br></div><div><br></div><div>So, do the ovn_nb and ovn_sb needs to be running previouly before pacemaker ovndb_servers resource create? Is there any such documentation referred?</div><div><br></div><div>2. Without your patch every nodes executing ovsdb_server_monitor and return OCF_SUCCESS </div><div><div>However, the first node of the three nodes cluster is executed ovsdb_server_stop action, the reason showed below:</div><div><27>Nov 28 15:35:11 node-1 pengine[1897010]: error: clone_color: ovndb_servers:0 is running on node-1.domain.tld which isn't allowed<br></div></div><div>Did I miss anything? I don't understand why it isn't allowed.</div><div><br></div><div>3. Regard your patch[1]</div><div>It first reports "/usr/lib/ocf/resource.d/ovn/ovndb-servers: line 26: ocf_attribute_target: command not found ]" in my environment(pacemaker 1.1.12)</div><div>The log showed same as item2, but I have seen very shortly different state from "pcs status" as below shown:</div><div><div> Master/Slave Set: ovndb_servers-master [ovndb_servers]</div><div> Slaves: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]</div></div><div>There is no promote action being executed.</div><div><br></div><div><br></div><div>Thanks for looking and help.</div><div><br></div><div><span style="font-size:12.8px">[1] - </span><a href="https://patchwork.ozlabs.org/patch/839022/" target="_blank" style="font-size:12.8px">https://patchwork.ozlabs.org/<wbr>patch/839022/</a><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 24, 2017 at 10:54 PM, Numan Siddique <span dir="ltr"><<a href="mailto:nusiddiq@redhat.com" target="_blank">nusiddiq@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Hui Xiang,<div><br></div><div>Can you please try with this patch [1] and see if it works for you ? Please let me know how it goes. But I am not sure, if the patch would fix the issue.</div><div><br></div><div>To brief, the OVN OCF script doesn't add monitor action for "Master" role. So pacemaker Resource agent would not check for the status of ovn db servers periodically. In case ovn db servers are killed, pacemaker wont know about it.</div><div><br></div><div><br></div><div><br></div><div><br></div><div>You can also take a look at this [1] to know how it is used in openstack with tripleo installation.</div><div><br></div><div>[1] - <a href="https://patchwork.ozlabs.org/patch/839022/" target="_blank">https://patchwork.ozlabs.org/<wbr>patch/839022/</a></div><div>[2] - <a href="https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/pacemaker/ovn_northd.pp" target="_blank">https://github.com/<wbr>openstack/puppet-tripleo/blob/<wbr>master/manifests/profile/<wbr>pacemaker/ovn_northd.pp</a></div><div><br></div><div><br></div><div>Thanks</div><div>Numan</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Nov 24, 2017 at 3:00 PM, Hui Xiang <span dir="ltr"><<a href="mailto:xianghuir@gmail.com" target="_blank">xianghuir@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi folks,<div><br></div><div> I am following what suggested on doc[1] to configure the ovndb_servers HA, however, it's so unluck with upgrading pacemaker packages from 1.12 to 1.16, do almost every kind of changes, there still not a ovndb_servers master promoted, is there any special recipe for it to run? so frustrated on it, sigh.</div><div><br></div><div>It always showed:</div><div><div> Master/Slave Set: ovndb_servers-master [ovndb_servers]</div><div> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]</div></div><div><br></div><div>Even if I tried below steps:</div><div>1. pcs resource debug-stop ovndb_server on every nodes. ovn-ctl status_ovnxb: running/backup </div><div>2. pcs resource debug-start ovndb_server on every nodes. ovn-ctl status_ovnxb: running/backup <br></div><div>3. pcs resource debug-promote ovndb_server on one nodes. ovn-ctl status_ovnxb: running/active<br></div><div><br></div><div>With above status, the pcs status still showed as:</div><div><div> Master/Slave Set: ovndb_servers-master [ovndb_servers]</div><div> Stopped: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]</div></div><div><br></div><div><br></div><div>[1]. <a href="https://github.com/openvswitch/ovs/blob/master/Documentation/topics/integration.rst" target="_blank">https://github.com/openvs<wbr>witch/ovs/blob/master/Document<wbr>ation/topics/integration.rst</a></div><div><br></div><div>Appreciated any hint.</div><div><br></div><div><br></div></div>
<br></div></div>______________________________<wbr>_________________<br>
discuss mailing list<br>
<a href="mailto:discuss@openvswitch.org" target="_blank">discuss@openvswitch.org</a><br>
<a href="https://mail.openvswitch.org/mailman/listinfo/ovs-discuss" rel="noreferrer" target="_blank">https://mail.openvswitch.org/m<wbr>ailman/listinfo/ovs-discuss</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>