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