Hi, this patch it's already available in the community version of gluster 3.12? In which version? If not, there is plan to backport it?
Greetings, Paolo Il 16/03/2018 13:24, Atin Mukherjee ha scritto: > Have sent a backport request https://review.gluster.org/19730 at > release-3.10 branch. Hopefully this fix will be picked up in next update. > > On Fri, Mar 16, 2018 at 4:47 PM, Marco Lorenzo Crociani > <mar...@prismatelecomtesting.com > <mailto:mar...@prismatelecomtesting.com>> wrote: > > Hi, > I'm hitting bug > https://bugzilla.redhat.com/show_bug.cgi?id=1442983 > <https://bugzilla.redhat.com/show_bug.cgi?id=1442983> > on glusterfs 3.10.11 and oVirt 4.1.9 (and before on glusterfs 3.8.14) > > The bug report says fixed in glusterfs-3.12.2-1 > > > The above is not a community bug. So even though the version says > 3.12.2 it's technically not the same community version of 3.12.2. What > I see this fix is introduced from glusterfs-3.13. If they can be > backported > > > Is there a plan to backport the fix to 3.10.x releases or the only > way to fix is upgrade to 3.12? > > Regards, > > -- > Marco Crociani > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org <mailto:Gluster-users@gluster.org> > http://lists.gluster.org/mailman/listinfo/gluster-users > <http://lists.gluster.org/mailman/listinfo/gluster-users> > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
