Re: [Gluster-devel] Release 5: Branched and further dates
On 10/04/2018 02:46 PM, Kotresh Hiremath Ravishankar wrote: > 2) Py3 corrections in master > > @Kotresh are all changes made to master backported to release-5 (may not > be merged, but looking at if they are backported and ready for merge)? > > > All changes made to master are backported to release-5. But py3 support > is still not complete. > So if run with Py3 the code may not work as intended? Looking for some clarification around "not complete" so that release notes can be amended accordingly. Thanks, Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 5: Branched and further dates
On Thu, Oct 4, 2018 at 2:47 PM Kotresh Hiremath Ravishankar < khire...@redhat.com> wrote: > > > On Thu, Oct 4, 2018 at 9:03 PM Shyam Ranganathan > wrote: > >> On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: >> > RC1 would be around 24th of Sep. with final release tagging around 1st >> > of Oct. >> >> RC1 now stands to be tagged tomorrow, and patches that are being >> targeted for a back port include, >> >> 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in >> mux cases) >> >> @RaBhat working on this. >> >> The following patch addresses the issue in release-5 branch. https://review.gluster.org/#/c/glusterfs/+/21347/ Regards, Raghavendra > 2) Py3 corrections in master >> >> @Kotresh are all changes made to master backported to release-5 (may not >> be merged, but looking at if they are backported and ready for merge)? >> > > All changes made to master are backported to release-5. But py3 support is > still not complete. > >> >> 3) Release notes review and updates with GD2 content pending >> >> @Kaushal/GD2 team can we get the updates as required? >> https://review.gluster.org/c/glusterfs/+/21303 >> >> 4) This bug [2] was filed when we released 4.0. >> >> The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options >> missing and hence post-upgrade clients failing the mount). This is >> possibly the last chance to fix it. >> >> Glusterd and protocol maintainers, can you chime in, if this bug needs >> to be and can be fixed? (thanks to @anoopcs for pointing it out to me) >> >> The tracker bug [1] does not have any other blockers against it, hence >> assuming we are not tracking/waiting on anything other than the set above. >> >> Thanks, >> Shyam >> >> [1] Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0 >> [2] Potential upgrade bug: >> https://bugzilla.redhat.com/show_bug.cgi?id=1540659 >> > > > -- > Thanks and Regards, > Kotresh H R > ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 5: Branched and further dates
On Thu, Oct 4, 2018 at 9:03 PM Shyam Ranganathan wrote: > On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: > > RC1 would be around 24th of Sep. with final release tagging around 1st > > of Oct. > > RC1 now stands to be tagged tomorrow, and patches that are being > targeted for a back port include, > > 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in > mux cases) > > @RaBhat working on this. > > 2) Py3 corrections in master > > @Kotresh are all changes made to master backported to release-5 (may not > be merged, but looking at if they are backported and ready for merge)? > All changes made to master are backported to release-5. But py3 support is still not complete. > > 3) Release notes review and updates with GD2 content pending > > @Kaushal/GD2 team can we get the updates as required? > https://review.gluster.org/c/glusterfs/+/21303 > > 4) This bug [2] was filed when we released 4.0. > > The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options > missing and hence post-upgrade clients failing the mount). This is > possibly the last chance to fix it. > > Glusterd and protocol maintainers, can you chime in, if this bug needs > to be and can be fixed? (thanks to @anoopcs for pointing it out to me) > > The tracker bug [1] does not have any other blockers against it, hence > assuming we are not tracking/waiting on anything other than the set above. > > Thanks, > Shyam > > [1] Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0 > [2] Potential upgrade bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1540659 > -- Thanks and Regards, Kotresh H R ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 5: Branched and further dates
On 10/04/2018 12:01 PM, Atin Mukherjee wrote: > 4) This bug [2] was filed when we released 4.0. > > The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options > missing and hence post-upgrade clients failing the mount). This is > possibly the last chance to fix it. > > Glusterd and protocol maintainers, can you chime in, if this bug needs > to be and can be fixed? (thanks to @anoopcs for pointing it out to me) > > > This is a bad bug to live with. OTOH, I do not have an immediate > solution in my mind on how to make sure (a) these options when > reintroduced are made no-ops, especially they will be disallowed to tune > (with out dirty option check hacks at volume set staging code) . If > we're to tag RC1 tomorrow, I wouldn't be able to take a risk to commit > this change. > > Can we actually have a note in our upgrade guide to document that if > you're upgrading to 4.1 or higher version make sure to disable these > options before the upgrade to mitigate this? Yes, adding this to the "Major Issues" section in the release notes as well as noting it in the upgrade guide is possible. I will go with this option for now, as we do not have complaints around this from 4.0/4.1 releases (which have the same issue as well). ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 5: Branched and further dates
On Thu, Oct 4, 2018 at 9:03 PM Shyam Ranganathan wrote: > On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: > > RC1 would be around 24th of Sep. with final release tagging around 1st > > of Oct. > > RC1 now stands to be tagged tomorrow, and patches that are being > targeted for a back port include, > > 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in > mux cases) > > @RaBhat working on this. > > 2) Py3 corrections in master > > @Kotresh are all changes made to master backported to release-5 (may not > be merged, but looking at if they are backported and ready for merge)? > > 3) Release notes review and updates with GD2 content pending > > @Kaushal/GD2 team can we get the updates as required? > https://review.gluster.org/c/glusterfs/+/21303 > > 4) This bug [2] was filed when we released 4.0. > > The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options > missing and hence post-upgrade clients failing the mount). This is > possibly the last chance to fix it. > > Glusterd and protocol maintainers, can you chime in, if this bug needs > to be and can be fixed? (thanks to @anoopcs for pointing it out to me) > This is a bad bug to live with. OTOH, I do not have an immediate solution in my mind on how to make sure (a) these options when reintroduced are made no-ops, especially they will be disallowed to tune (with out dirty option check hacks at volume set staging code) . If we're to tag RC1 tomorrow, I wouldn't be able to take a risk to commit this change. Can we actually have a note in our upgrade guide to document that if you're upgrading to 4.1 or higher version make sure to disable these options before the upgrade to mitigate this? > The tracker bug [1] does not have any other blockers against it, hence > assuming we are not tracking/waiting on anything other than the set above. > > Thanks, > Shyam > > [1] Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0 > [2] Potential upgrade bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1540659 > ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 5: Branched and further dates
On 09/13/2018 11:10 AM, Shyam Ranganathan wrote: > RC1 would be around 24th of Sep. with final release tagging around 1st > of Oct. RC1 now stands to be tagged tomorrow, and patches that are being targeted for a back port include, 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in mux cases) @RaBhat working on this. 2) Py3 corrections in master @Kotresh are all changes made to master backported to release-5 (may not be merged, but looking at if they are backported and ready for merge)? 3) Release notes review and updates with GD2 content pending @Kaushal/GD2 team can we get the updates as required? https://review.gluster.org/c/glusterfs/+/21303 4) This bug [2] was filed when we released 4.0. The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options missing and hence post-upgrade clients failing the mount). This is possibly the last chance to fix it. Glusterd and protocol maintainers, can you chime in, if this bug needs to be and can be fixed? (thanks to @anoopcs for pointing it out to me) The tracker bug [1] does not have any other blockers against it, hence assuming we are not tracking/waiting on anything other than the set above. Thanks, Shyam [1] Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0 [2] Potential upgrade bug: https://bugzilla.redhat.com/show_bug.cgi?id=1540659 ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Release 5: Branched and further dates
Hi, Release 5 has been branched today. To backport fixes to the upcoming 5.0 release use the tracker bug [1]. We intend to roll out RC0 build by end of tomorrow for testing, unless the set of usual cleanup patches (op-version, some messages, gfapi version) land in any form of trouble. RC1 would be around 24th of Sep. with final release tagging around 1st of Oct. I would like to encourage everyone to test out the bits as appropriate and post updates to this thread. Thanks, Shyam [1] 5.0 tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0 ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
