<div dir="ltr"><div>Fixes on master (before or after the release-7 branch was taken) almost certainly warrant a backport IMO to at least release-6, and probably release-5 as well.<br></div><div><br></div><div>We used to have a "tracker" BZ for each minor release (e.g. 6.6) to keep track of backports by cloning the original BZ and changing the Version, and adding that BZ to the tracker. I'm not sure what happened to that practice. The last ones I can find are for 6.3 and 5.7; <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-6.3">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-6.3</a> and <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.7">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.7</a></div><div><br></div><div>It isn't enough to just backport recent fixes on master to release-7. We are supposedly continuing to maintain release-6 and release-5 after release-7 GAs. If that has changed, I haven't seen an announcement to that effect. I don't know why our developers don't automatically backport to all the actively maintained releases.<br></div><div><br></div><div>Even if there isn't a tracker BZ, you can always create a backport BZ by cloning the original BZ and change the release to 6. That'd be a good place to start.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 1, 2019 at 8:45 AM Alexander Iliev <<a href="mailto:ailiev%2Bgluster@mamul.org">ailiev+gluster@mamul.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Strahil,<br>
<br>
Yes, this might be right, but I would still expect fixes like this to be <br>
released for all supported major versions (which should include 6.) At <br>
least that's how I understand <a href="https://www.gluster.org/release-schedule/" rel="noreferrer" target="_blank">https://www.gluster.org/release-schedule/</a>.<br>
<br>
Anyway, let's wait for Sunny to clarify.<br>
<br>
Best regards,<br>
alexander iliev<br>
<br>
On 9/1/19 2:07 PM, Strahil Nikolov wrote:<br>
> Hi Alex,<br>
> <br>
> I'm not very deep into bugzilla stuff, but for me NEXTRELEASE means v7.<br>
> <br>
> Sunny,<br>
> Am I understanding it correctly ?<br>
> <br>
> Best Regards,<br>
> Strahil Nikolov<br>
> <br>
> В неделя, 1 септември 2019 г., 14:27:32 ч. Гринуич+3, Alexander Iliev <br>
> <<a href="mailto:ailiev%2Bgluster@mamul.org" target="_blank">ailiev+gluster@mamul.org</a>> написа:<br>
> <br>
> <br>
> Hi Sunny,<br>
> <br>
> Thank you for the quick response.<br>
> <br>
> It's not clear to me however if the fix has been already released or not.<br>
> <br>
> The bug status is CLOSED NEXTRELEASE and according to [1] the<br>
> NEXTRELEASE resolution means that the fix will be included in the next<br>
> supported release. The bug is logged against the mainline version<br>
> though, so I'm not sure what this means exactly.<br>
> <br>
> From the 6.4[2] and 6.5[3] release notes it seems it hasn't been<br>
> released yet.<br>
> <br>
> Ideally I would not like to patch my systems locally, so if you have an<br>
> ETA on when this will be out officially I would really appreciate it.<br>
> <br>
> Links:<br>
> [1] <a href="https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status</a><br>
> [2] <a href="https://docs.gluster.org/en/latest/release-notes/6.4/" rel="noreferrer" target="_blank">https://docs.gluster.org/en/latest/release-notes/6.4/</a><br>
> [3] <a href="https://docs.gluster.org/en/latest/release-notes/6.5/" rel="noreferrer" target="_blank">https://docs.gluster.org/en/latest/release-notes/6.5/</a><br>
> <br>
> Thank you!<br>
> <br>
> Best regards,<br>
> <br>
> alexander iliev<br>
> <br>
> On 8/30/19 9:22 AM, Sunny Kumar wrote:<br>
> > Hi Alexander,<br>
> ><br>
> > Thanks for pointing that out!<br>
> ><br>
> > But this issue is fixed now you can see below link for bz-link and patch.<br>
> ><br>
> > BZ - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1709248" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1709248</a><br>
> ><br>
> > Patch - <a href="https://review.gluster.org/#/c/glusterfs/+/22716/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c/glusterfs/+/22716/</a><br>
> ><br>
> > Hope this helps.<br>
> ><br>
> > /sunny<br>
> ><br>
> > On Fri, Aug 30, 2019 at 2:30 AM Alexander Iliev<br>
> > <<a href="mailto:ailiev%2Bgluster@mamul.org" target="_blank">ailiev+gluster@mamul.org</a> <mailto:<a href="mailto:gluster@mamul.org" target="_blank">gluster@mamul.org</a>>> wrote:<br>
> >><br>
> >> Hello dear GlusterFS users list,<br>
> >><br>
> >> I have been trying to set up geo-replication between two clusters for<br>
> >> some time now. The desired state is (Cluster #1) being replicated to<br>
> >> (Cluster #2).<br>
> >><br>
> >> Here are some details about the setup:<br>
> >><br>
> >> Cluster #1: three nodes connected via a local network (<a href="http://172.31.35.0/24" rel="noreferrer" target="_blank">172.31.35.0/24</a>),<br>
> >> one replicated (3 replica) volume.<br>
> >><br>
> >> Cluster #2: three nodes connected via a local network (<a href="http://172.31.36.0/24" rel="noreferrer" target="_blank">172.31.36.0/24</a>),<br>
> >> one replicated (3 replica) volume.<br>
> >><br>
> >> The two clusters are connected to the Internet via separate network<br>
> >> adapters.<br>
> >><br>
> >> Only SSH (port 22) is open on cluster #2 nodes' adapters connected to<br>
> >> the Internet.<br>
> >><br>
> >> All nodes are running Ubuntu 18.04 and GlusterFS 6.3 installed from [1].<br>
> >><br>
> >> The first time I followed the guide[2] everything went fine up until I<br>
> >> reached the "Create the session" step. That was like a month ago, then I<br>
> >> had to temporarily stop working in this and now I am coming back to it.<br>
> >><br>
> >> Currently, if I try to see the mountbroker status I get the following:<br>
> >><br>
> >>> # gluster-mountbroker status<br>
> >>> Traceback (most recent call last):<br>
> >>> File "/usr/sbin/gluster-mountbroker", line 396, in <module><br>
> >>> runcli()<br>
> >>> File <br>
> "/usr/lib/python3/dist-packages/gluster/cliutils/cliutils.py", line 225, <br>
> in runcli<br>
> >>> cls.run(args)<br>
> >>> File "/usr/sbin/gluster-mountbroker", line 275, in run<br>
> >>> out = execute_in_peers("node-status")<br>
> >>> File "/usr/lib/python3/dist-packages/gluster/cliutils/cliutils.py",<br>
> >> line 127, in execute_in_peers<br>
> >>> raise GlusterCmdException((rc, out, err, " ".join(cmd)))<br>
> >>> gluster.cliutils.cliutils.GlusterCmdException: (1, '', 'Unable to<br>
> >> end. Error : Success\n', 'gluster system:: execute mountbroker.py<br>
> >> node-status')<br>
> >><br>
> >> And in /var/log/gluster/glusterd.log I have:<br>
> >><br>
> >>> [2019-08-10 15:24:21.418834] E [MSGID: 106336]<br>
> >> [glusterd-geo-rep.c:5413:glusterd_op_sys_exec] 0-management: Unable to<br>
> >> end. Error : Success<br>
> >>> [2019-08-10 15:24:21.418908] E [MSGID: 106122]<br>
> >> [glusterd-syncop.c:1445:gd_commit_op_phase] 0-management: Commit of<br>
> >> operation 'Volume Execute system commands' failed on localhost : Unable<br>
> >> to end. Error : Success<br>
> >><br>
> >> So, I have two questions right now:<br>
> >><br>
> >> 1) Is there anything wrong with my setup (networking, open ports, etc.)?<br>
> >> Is it expected to work with this setup or should I redo it in a<br>
> >> different way?<br>
> >> 2) How can I troubleshoot the current status of my setup? Can I find out<br>
> >> what's missing/wrong and continue from there or should I just start from<br>
> >> scratch?<br>
> >><br>
> >> Links:<br>
> >> [1] <a href="http://ppa.launchpad.net/gluster/glusterfs-6/ubuntu" rel="noreferrer" target="_blank">http://ppa.launchpad.net/gluster/glusterfs-6/ubuntu</a><br>
> >> [2]<br>
> >> <br>
> <a href="https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/" rel="noreferrer" target="_blank">https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/</a><br>
> >><br>
> >> Thank you!<br>
> >><br>
> >> Best regards,<br>
> >> --<br>
> >> alexander iliev<br>
> >> _______________________________________________<br>
> >> Gluster-users mailing list<br>
> >> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
> >> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>