[Gluster-devel] gluster-ansible: current status
Hi, We didn't have any new builds since more than a week. This week is more of bug fixes and testing. * We have been testing quite a bit since last week. * Few new bugs have been found and fixed: https://tinyurl.com/yc3wyugt * Testing setup with molecule is complete and ready to merge. -sac ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Gluster Weekly Report : Static Analyser
Hello folks, The current status of static analyser is below: Coverity scan status: Last week we started from 180 and now its 163 (oct 5). Major contributors - Susant (3 patches) and Sunny (3 patches). Clang-scan status: Last week we started 119 and today its 110. Major contributors - Iraj and Harpreet. If you want to contribute in fixing coverity and clang-scan fixes please follow these instruction: * for coverity scan fixes: https://lists.gluster.org/pipermail/gluster-devel/2018-August/055155.html * for clang-scan: https://lists.gluster.org/pipermail/gluster-devel/2018-August/055212.html Regards, Sunny kumar ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] 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 ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] 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 > > maintain...@gluster.org > > https://lists.gluster.org/mailman/listinfo/maintainers > > > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > -- - Atin (atinm) ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] 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 > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] ./rfc.sh not pushing patch to gerrit
What is the agreed upon clang version for Glusterfs project? Is it clang-6? On Fri, Oct 5, 2018 at 1:58 PM Raghavendra Gowdappa wrote: > clang-4.0.1 pushes patch, but still doesn't understand some keys in > clang-format. > > [rgowdapp@rgowdapp glusterfs]$ ./rfc.sh > [detached HEAD 401a7b6] cluster/dht: clang-format dht-common.c > 1 file changed, 10674 insertions(+), 11166 deletions(-) > rewrite xlators/cluster/dht/src/dht-common.c (88%) > [detached HEAD 2bf5031] cluster/dht: fixes to unlinking invalid linkto file > 1 file changed, 236 insertions(+), 268 deletions(-) > Successfully rebased and updated refs/heads/1635145. > YAML:35:23: error: unknown key 'SplitEmptyFunction' > SplitEmptyFunction: true > ^~~~ > > > On Fri, Oct 5, 2018 at 10:47 AM Raghavendra Gowdappa > wrote: > >> We should document (better still add checks in rfc.sh and warn user to >> upgrade) that we need clang version x or greater. >> >> On Fri, Oct 5, 2018 at 10:45 AM Sachidananda URS wrote: >> >>> >>> >>> On Fri, Oct 5, 2018 at 10:41 AM, Raghavendra Gowdappa < >>> rgowd...@redhat.com> wrote: >>> General options: -help - Display available options (-help-hidden for more) -help-list- Display list of available options (-help-list-hidden for more) -version - Display the version of this program [rgowdapp@rgowdapp ~]$ clang-format -version ; echo $? LLVM (http://llvm.org/): LLVM version 3.4.2 Optimized build. Built Dec 7 2015 (09:37:36). Default target: x86_64-redhat-linux-gnu Host CPU: x86-64 1 >>> It is a bug then, which they've fixed later on. Upgrade is the only >>> choice. >>> >>> ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] ./rfc.sh not pushing patch to gerrit
clang-4.0.1 pushes patch, but still doesn't understand some keys in clang-format. [rgowdapp@rgowdapp glusterfs]$ ./rfc.sh [detached HEAD 401a7b6] cluster/dht: clang-format dht-common.c 1 file changed, 10674 insertions(+), 11166 deletions(-) rewrite xlators/cluster/dht/src/dht-common.c (88%) [detached HEAD 2bf5031] cluster/dht: fixes to unlinking invalid linkto file 1 file changed, 236 insertions(+), 268 deletions(-) Successfully rebased and updated refs/heads/1635145. YAML:35:23: error: unknown key 'SplitEmptyFunction' SplitEmptyFunction: true ^~~~ On Fri, Oct 5, 2018 at 10:47 AM Raghavendra Gowdappa wrote: > We should document (better still add checks in rfc.sh and warn user to > upgrade) that we need clang version x or greater. > > On Fri, Oct 5, 2018 at 10:45 AM Sachidananda URS wrote: > >> >> >> On Fri, Oct 5, 2018 at 10:41 AM, Raghavendra Gowdappa < >> rgowd...@redhat.com> wrote: >> >>> General options: >>> >>> -help - Display available options (-help-hidden >>> for more) >>> -help-list- Display list of available options >>> (-help-list-hidden for more) >>> -version - Display the version of this program >>> [rgowdapp@rgowdapp ~]$ clang-format -version ; echo $? >>> LLVM (http://llvm.org/): >>> LLVM version 3.4.2 >>> Optimized build. >>> Built Dec 7 2015 (09:37:36). >>> Default target: x86_64-redhat-linux-gnu >>> Host CPU: x86-64 >>> 1 >>> >>> >> It is a bug then, which they've fixed later on. Upgrade is the only >> choice. >> >> ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
