Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On 10/05/2018 08:29 PM, Shyam Ranganathan wrote: On 10/04/2018 11:33 AM, 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, We still are awaiting release notes (other than the bugs section) to be closed. There is one new bug that needs attention from the replicate team. https://bugzilla.redhat.com/show_bug.cgi?id=1636502 The above looks important to me to be fixed before the release, @ravi or @pranith can you take a look? I've attempted a fix @ https://review.gluster.org/#/c/glusterfs/+/21366/ -Ravi 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in mux cases) @RaBhat working on this. Done 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)? Done, release notes amend pending 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 Still awaiting this. 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) Release notes to be corrected to call this out. 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 ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
Had forgot to add milind, ccing. On Mon, Oct 8, 2018 at 11:41 AM Kotresh Hiremath Ravishankar < khire...@redhat.com> wrote: > > > On Fri, Oct 5, 2018 at 10:31 PM Shyam Ranganathan > wrote: > >> On 10/05/2018 10:59 AM, Shyam Ranganathan wrote: >> > On 10/04/2018 11:33 AM, 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, >> > We still are awaiting release notes (other than the bugs section) to be >> > closed. >> > >> > There is one new bug that needs attention from the replicate team. >> > https://bugzilla.redhat.com/show_bug.cgi?id=1636502 >> > >> > The above looks important to me to be fixed before the release, @ravi or >> > @pranith can you take a look? >> > >> >> RC1 is tagged and release tarball generated. >> >> We still have 2 issues to work on, >> >> 1. The above messages from AFR in self heal logs >> >> 2. We need to test with Py3, else we risk putting out packages there on >> Py3 default distros and causing some mayhem if basic things fail. >> >> I am open to suggestions on how to ensure we work with Py3, thoughts? >> >> I am thinking we run a regression on F28 (or a platform that defaults to >> Py3) and ensure regressions are passing at the very least. For other >> Python code that regressions do not cover, >> - We have a list at [1] >> - How can we split ownership of these? >> > > +1 for the regression run on py3 default platform. We don't need to run > full regressions. > We can chose to run only those test cases related to python. Categorically > we have > 1. geo-rep > 2. events framework > 3. glusterfind > 4. tools/scripts > > I can take care of geo-rep. With following two patches, geo-rep works both > on py2 and py3. > I have tested these locally on centos-7.5 (py2 is default) and fedora28 > (making py3 default by > symlink /usr/bin/python -> python3). Again the test was very basic, we can > fix going forward, > if there are any corner cases. > > 1. https://review.gluster.org/#/c/glusterfs/+/21356/ (Though this is > events patch, geo-rep internally uses it, so is required for geo-rep.) > 2. https://review.gluster.org/#/c/glusterfs/+/21357/ > > It think we need to add regression tests for events and glusterfind. > Adding milind to comment on glusterfind. > >> >> @Aravinda, @Kotresh, and @ppai, looking to you folks to help out with >> the process and needs here. >> >> Shyam >> >> [1] https://github.com/gluster/glusterfs/issues/411 >> > > > -- > Thanks and Regards, > Kotresh H R > -- Thanks and Regards, Kotresh H R ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On Fri, Oct 5, 2018 at 10:31 PM Shyam Ranganathan wrote: > On 10/05/2018 10:59 AM, Shyam Ranganathan wrote: > > On 10/04/2018 11:33 AM, 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, > > We still are awaiting release notes (other than the bugs section) to be > > closed. > > > > There is one new bug that needs attention from the replicate team. > > https://bugzilla.redhat.com/show_bug.cgi?id=1636502 > > > > The above looks important to me to be fixed before the release, @ravi or > > @pranith can you take a look? > > > > RC1 is tagged and release tarball generated. > > We still have 2 issues to work on, > > 1. The above messages from AFR in self heal logs > > 2. We need to test with Py3, else we risk putting out packages there on > Py3 default distros and causing some mayhem if basic things fail. > > I am open to suggestions on how to ensure we work with Py3, thoughts? > > I am thinking we run a regression on F28 (or a platform that defaults to > Py3) and ensure regressions are passing at the very least. For other > Python code that regressions do not cover, > - We have a list at [1] > - How can we split ownership of these? > +1 for the regression run on py3 default platform. We don't need to run full regressions. We can chose to run only those test cases related to python. Categorically we have 1. geo-rep 2. events framework 3. glusterfind 4. tools/scripts I can take care of geo-rep. With following two patches, geo-rep works both on py2 and py3. I have tested these locally on centos-7.5 (py2 is default) and fedora28 (making py3 default by symlink /usr/bin/python -> python3). Again the test was very basic, we can fix going forward, if there are any corner cases. 1. https://review.gluster.org/#/c/glusterfs/+/21356/ (Though this is events patch, geo-rep internally uses it, so is required for geo-rep.) 2. https://review.gluster.org/#/c/glusterfs/+/21357/ It think we need to add regression tests for events and glusterfind. Adding milind to comment on glusterfind. > > @Aravinda, @Kotresh, and @ppai, looking to you folks to help out with > the process and needs here. > > Shyam > > [1] https://github.com/gluster/glusterfs/issues/411 > -- Thanks and Regards, Kotresh H R ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On 10/05/2018 10:59 AM, Shyam Ranganathan wrote: > On 10/04/2018 11:33 AM, 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, > We still are awaiting release notes (other than the bugs section) to be > closed. > > There is one new bug that needs attention from the replicate team. > https://bugzilla.redhat.com/show_bug.cgi?id=1636502 > > The above looks important to me to be fixed before the release, @ravi or > @pranith can you take a look? > RC1 is tagged and release tarball generated. We still have 2 issues to work on, 1. The above messages from AFR in self heal logs 2. We need to test with Py3, else we risk putting out packages there on Py3 default distros and causing some mayhem if basic things fail. I am open to suggestions on how to ensure we work with Py3, thoughts? I am thinking we run a regression on F28 (or a platform that defaults to Py3) and ensure regressions are passing at the very least. For other Python code that regressions do not cover, - We have a list at [1] - How can we split ownership of these? @Aravinda, @Kotresh, and @ppai, looking to you folks to help out with the process and needs here. Shyam [1] https://github.com/gluster/glusterfs/issues/411 ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On 10/05/2018 11:04 AM, Atin Mukherjee wrote: > > > > 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 > > Still awaiting this. > > > Kaushal has added a comment into the patch providing the content today > morning IST. Any additional details are you looking for? Saw this now, this should be fine. I did not read comments in my morning (my bad), and instead saw there was no activity on the patch itself, and missed this. Thanks, Shyam ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On Fri, 5 Oct 2018 at 20:29, Shyam Ranganathan wrote: > On 10/04/2018 11:33 AM, 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, > > We still are awaiting release notes (other than the bugs section) to be > closed. > > There is one new bug that needs attention from the replicate team. > https://bugzilla.redhat.com/show_bug.cgi?id=1636502 > > The above looks important to me to be fixed before the release, @ravi or > @pranith can you take a look? > > > > > 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in > > mux cases) > > > > @RaBhat working on this. > > Done > > > > > 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)? > > Done, release notes amend pending > > > > > 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 > > Still awaiting this. Kaushal has added a comment into the patch providing the content today morning IST. Any additional details are you looking for? > > > > > 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) > > Release notes to be corrected to call this out. > > > > > 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 > > ___ > > maintainers mailing list > > maintainers@gluster.org > > https://lists.gluster.org/mailman/listinfo/maintainers > > > ___ > maintainers mailing list > maintainers@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > -- - Atin (atinm) ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On 10/04/2018 11:33 AM, 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, We still are awaiting release notes (other than the bugs section) to be closed. There is one new bug that needs attention from the replicate team. https://bugzilla.redhat.com/show_bug.cgi?id=1636502 The above looks important to me to be fixed before the release, @ravi or @pranith can you take a look? > > 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in > mux cases) > > @RaBhat working on this. Done > > 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)? Done, release notes amend pending > > 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 Still awaiting this. > > 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) Release notes to be corrected to call this out. > > 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 > ___ > maintainers mailing list > maintainers@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [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 ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [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 > ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [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 ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [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). ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [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 > ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [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 ___ maintainers mailing list maintainers@gluster.org https://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
On Wed, Sep 26, 2018 at 7:53 PM Shyam Ranganathan
wrote:
> Hi,
>
> Updates on the release and shout out for help is as follows,
>
> RC0 Release packages for testing are available see the thread at [1]
>
> These are the following activities that we need to complete for calling
> the release as GA (with no major regressions i.e):
>
> 1. Release notes (Owner: release owner (myself), will send out an
> initial version for review and to solicit inputs today)
>
> 2. Testing dashboard to maintain release health (new, thanks Nigel)
> - Dashboard at [2]
> - We already have 3 failures here as follows, needs attention from
> appropriate *maintainers*,
> (a)
>
> https://build.gluster.org/job/regression-test-with-multiplex/871/consoleText
> - Failed with core:
> ./tests/basic/afr/gfid-mismatch-resolution-with-cli.t
> (b)
>
> https://build.gluster.org/job/regression-test-with-multiplex/873/consoleText
> - Failed with core: ./tests/bugs/snapshot/bug-1275616.t
> - Also test ./tests/bugs/glusterd/validating-server-quorum.t had
> to be
> retried
>
The test case ./tests/bugs/glusterd/validating-server-quorum.t had to be
retried since, it got timed out at the first run.
I went through the logs of first run, everything looks fine. Looking at all
the time stamps, got to know that cluster_brick_up_status took 45sec
(PROCESS_UP_TIMEOUT) most of the times when it is used. As we clubbed many
of the glusterd test cases into a single test case, the test case might
need some more time to execute. If this test case gets timed out
repeatedly, we will think of the actions need to be taken.
Definition of cluster_brick_up_status for your reference:
function cluster_brick_up_status {
local vol=$2
local host=$3
local brick=$4
eval \$CLI_$1 volume status $vol $host:$brick --xml | sed -ne
's/.*\([01]\)<\/status>/\1/p'
}
(c)
> https://build.gluster.org/job/regression-test-burn-in/4109/consoleText
> - Failed with core: ./tests/basic/mgmt_v3-locks.t
>
> 3. Upgrade testing
> - Need *volunteers* to do the upgrade testing as stated in the 4.1
> upgrade guide [3] to note any differences or changes to the same
> - Explicit call out on *disperse* volumes, as we continue to state
> online upgrade is not possible, is this addressed and can this be tested
> and the documentation improved around the same?
>
> 4. Performance testing/benchmarking
> - I would be using smallfile and FIO to baseline 3.12 and 4.1 and test
> RC0 for any major regressions
> - If we already know of any please shout out so that we are aware of
> the problems and upcoming fixes to the same
>
> 5. Major testing areas
> - Py3 support: Need *volunteers* here to test out the Py3 support
> around changed python files, if there is not enough coverage in the
> regression test suite for the same
>
> Thanks,
> Shyam
>
> [1] Packages for RC0:
> https://lists.gluster.org/pipermail/maintainers/2018-September/005044.html
>
> [2] Release testing health dashboard:
> https://build.gluster.org/job/nightly-release-5/
>
> [3] 4.1 upgrade guide:
> https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
>
> On 09/13/2018 11:10 AM, Shyam Ranganathan wrote:
> > 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
> > ___
> > maintainers mailing list
> > maintainers@gluster.org
> > https://lists.gluster.org/mailman/listinfo/maintainers
> >
> ___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
--
Thanks,
Sanju
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers
