<html><head></head><body><div class="ydpbbd88aabyahoo-style-wrap" style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:16px;"><div></div>
        <div dir="ltr" data-setdir="false">Hi Alex,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I'm not very deep into bugzilla stuff, but for me NEXTRELEASE means v7.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Sunny,</div><div dir="ltr" data-setdir="false">Am I understanding it correctly ?</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Best Regards,</div><div dir="ltr" data-setdir="false">Strahil Nikolov</div><div><br></div>
        
        </div><div id="ydpffe1a3yahoo_quoted_7755114696" class="ydpffe1a3yahoo_quoted">
            <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
                
                <div>
                    В неделя, 1 септември 2019 г., 14:27:32 ч. Гринуич+3, Alexander Iliev &lt;ailiev+gluster@mamul.org&gt; написа:
                </div>
                <div><br></div>
                <div><br></div>
                <div><div dir="ltr">Hi Sunny,<br clear="none"><br clear="none">Thank you for the quick response.<br clear="none"><br clear="none">It's not clear to me however if the fix has been already released or not.<br clear="none"><br clear="none">The bug status is CLOSED NEXTRELEASE and according to [1] the <br clear="none">NEXTRELEASE resolution means that the fix will be included in the next <br clear="none">supported release. The bug is logged against the mainline version <br clear="none">though, so I'm not sure what this means exactly.<br clear="none"><br clear="none"> From the 6.4[2] and 6.5[3] release notes it seems it hasn't been <br clear="none">released yet.<br clear="none"><br clear="none">Ideally I would not like to patch my systems locally, so if you have an <br clear="none">ETA on when this will be out officially I would really appreciate it.<br clear="none"><br clear="none">Links:<br clear="none">[1] <a shape="rect" href="https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status" rel="nofollow" target="_blank">https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status</a><br clear="none">[2] <a shape="rect" href="https://docs.gluster.org/en/latest/release-notes/6.4/" rel="nofollow" target="_blank">https://docs.gluster.org/en/latest/release-notes/6.4/</a><br clear="none">[3] <a shape="rect" href="https://docs.gluster.org/en/latest/release-notes/6.5/" rel="nofollow" target="_blank">https://docs.gluster.org/en/latest/release-notes/6.5/</a><br clear="none"><br clear="none">Thank you!<br clear="none"><br clear="none">Best regards,<br clear="none"><br clear="none">alexander iliev<br clear="none"><div class="ydpffe1a3yqt9545796684" id="ydpffe1a3yqtfd27945"><br clear="none">On 8/30/19 9:22 AM, Sunny Kumar wrote:<br clear="none">&gt; Hi Alexander,<br clear="none">&gt; <br clear="none">&gt; Thanks for pointing that out!<br clear="none">&gt; <br clear="none">&gt; But this issue is fixed now you can see below link for bz-link and patch.<br clear="none">&gt; <br clear="none">&gt; BZ - <a shape="rect" href="https://bugzilla.redhat.com/show_bug.cgi?id=1709248" rel="nofollow" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1709248</a><br clear="none">&gt; <br clear="none">&gt; Patch - <a shape="rect" href="https://review.gluster.org/#/c/glusterfs/+/22716/" rel="nofollow" target="_blank">https://review.gluster.org/#/c/glusterfs/+/22716/</a><br clear="none">&gt; <br clear="none">&gt; Hope this helps.<br clear="none">&gt; <br clear="none">&gt; /sunny<br clear="none">&gt; <br clear="none">&gt; On Fri, Aug 30, 2019 at 2:30 AM Alexander Iliev<br clear="none">&gt; &lt;ailiev+<a shape="rect" href="mailto:gluster@mamul.org" rel="nofollow" target="_blank">gluster@mamul.org</a>&gt; wrote:<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Hello dear GlusterFS users list,<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; I have been trying to set up geo-replication between two clusters for<br clear="none">&gt;&gt; some time now. The desired state is (Cluster #1) being replicated to<br clear="none">&gt;&gt; (Cluster #2).<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Here are some details about the setup:<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Cluster #1: three nodes connected via a local network (172.31.35.0/24),<br clear="none">&gt;&gt; one replicated (3 replica) volume.<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Cluster #2: three nodes connected via a local network (172.31.36.0/24),<br clear="none">&gt;&gt; one replicated (3 replica) volume.<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; The two clusters are connected to the Internet via separate network<br clear="none">&gt;&gt; adapters.<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Only SSH (port 22) is open on cluster #2 nodes' adapters connected to<br clear="none">&gt;&gt; the Internet.<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; All nodes are running Ubuntu 18.04 and GlusterFS 6.3 installed from [1].<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; The first time I followed the guide[2] everything went fine up until I<br clear="none">&gt;&gt; reached the "Create the session" step. That was like a month ago, then I<br clear="none">&gt;&gt; had to temporarily stop working in this and now I am coming back to it.<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Currently, if I try to see the mountbroker status I get the following:<br clear="none">&gt;&gt;<br clear="none">&gt;&gt;&gt; # gluster-mountbroker status<br clear="none">&gt;&gt;&gt; Traceback (most recent call last):<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; File "/usr/sbin/gluster-mountbroker", line 396, in &lt;module&gt;<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; runcli()<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; File "/usr/lib/python3/dist-packages/gluster/cliutils/cliutils.py", line 225, in runcli<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; cls.run(args)<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; File "/usr/sbin/gluster-mountbroker", line 275, in run<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; out = execute_in_peers("node-status")<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; File "/usr/lib/python3/dist-packages/gluster/cliutils/cliutils.py",<br clear="none">&gt;&gt; line 127, in execute_in_peers<br clear="none">&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; raise GlusterCmdException((rc, out, err, " ".join(cmd)))<br clear="none">&gt;&gt;&gt; gluster.cliutils.cliutils.GlusterCmdException: (1, '', 'Unable to<br clear="none">&gt;&gt; end. Error : Success\n', 'gluster system:: execute mountbroker.py<br clear="none">&gt;&gt; node-status')<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; And in /var/log/gluster/glusterd.log I have:<br clear="none">&gt;&gt;<br clear="none">&gt;&gt;&gt; [2019-08-10 15:24:21.418834] E [MSGID: 106336]<br clear="none">&gt;&gt; [glusterd-geo-rep.c:5413:glusterd_op_sys_exec] 0-management: Unable to<br clear="none">&gt;&gt; end. Error : Success<br clear="none">&gt;&gt;&gt; [2019-08-10 15:24:21.418908] E [MSGID: 106122]<br clear="none">&gt;&gt; [glusterd-syncop.c:1445:gd_commit_op_phase] 0-management: Commit of<br clear="none">&gt;&gt; operation 'Volume Execute system commands' failed on localhost : Unable<br clear="none">&gt;&gt; to end. Error : Success<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; So, I have two questions right now:<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; 1) Is there anything wrong with my setup (networking, open ports, etc.)?<br clear="none">&gt;&gt; Is it expected to work with this setup or should I redo it in a<br clear="none">&gt;&gt; different way?<br clear="none">&gt;&gt; 2) How can I troubleshoot the current status of my setup? Can I find out<br clear="none">&gt;&gt; what's missing/wrong and continue from there or should I just start from<br clear="none">&gt;&gt; scratch?<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Links:<br clear="none">&gt;&gt; [1] <a shape="rect" href="http://ppa.launchpad.net/gluster/glusterfs-6/ubuntu" rel="nofollow" target="_blank">http://ppa.launchpad.net/gluster/glusterfs-6/ubuntu</a><br clear="none">&gt;&gt; [2]<br clear="none">&gt;&gt; <a shape="rect" href="https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/" rel="nofollow" target="_blank">https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/</a><br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Thank you!<br clear="none">&gt;&gt;<br clear="none">&gt;&gt; Best regards,<br clear="none">&gt;&gt; --<br clear="none">&gt;&gt; alexander iliev<br clear="none">&gt;&gt; _______________________________________________<br clear="none">&gt;&gt; Gluster-users mailing list<br clear="none">&gt;&gt; <a shape="rect" href="mailto:Gluster-users@gluster.org" rel="nofollow" target="_blank">Gluster-users@gluster.org</a><br clear="none">&gt;&gt; <a shape="rect" href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="nofollow" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br clear="none">_______________________________________________<br clear="none">Gluster-users mailing list<br clear="none"><a shape="rect" href="mailto:Gluster-users@gluster.org" rel="nofollow" target="_blank">Gluster-users@gluster.org</a><br clear="none"><a shape="rect" href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="nofollow" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br clear="none"></div></div></div>
            </div>
        </div></body></html>