From surs at redhat.com  Tue Feb  5 11:31:04 2019
From: surs at redhat.com (Sachidananda URS)
Date: Tue, 5 Feb 2019 17:01:04 +0530
Subject: [gluster-packaging] gdeploy-2.0.11 available for testing
In-Reply-To: <20190131113629.GP2414@ndevos-x270.lan.nixpanic.net>
References: <20190129105614.GC2414@ndevos-x270.lan.nixpanic.net>
	<CAA3LYT+rbNDUUDwiAGuUJxct+CRj7-V4NCZQExBQJi8VJgG_dg@mail.gmail.com>
	<20190131085712.GM2414@ndevos-x270.lan.nixpanic.net>
	<CAE44-AtrMpQDf8XYANu3vp6KJgJHJt+LMbL_+xo1jd8yM2RCLg@mail.gmail.com>
	<20190131113629.GP2414@ndevos-x270.lan.nixpanic.net>
Message-ID: <CAE44-AvpB8=qeXEESe8zFVC6ABsuv3z_CdEZnL5eDgYurf6vTA@mail.gmail.com>

On Thu, Jan 31, 2019 at 5:06 PM Niels de Vos <ndevos at redhat.com> wrote:

> On Thu, Jan 31, 2019 at 02:48:13PM +0530, Sachidananda URS wrote:
> > On Thu, Jan 31, 2019 at 2:27 PM Niels de Vos <ndevos at redhat.com> wrote:
> >
> > > On Thu, Jan 31, 2019 at 09:37:15AM +0530, Ramakrishna Reddy Yekulla
> wrote:
> > > > On Tue, Jan 29, 2019 at 4:26 PM Niels de Vos <ndevos at redhat.com>
> wrote:
> > > >
> > > > > gdeploy-2.0.11-1.el7 is available in the centos-gluster*-test
> > > > > repositories from the CentOS Storage SIG. Please test the update
> and
> > > let
> > > > > me know when the package can be marked for release.
> > > > >
> > > > >   # yum install centos-release-gluster
> > > > >   # yum install --enablerepo=centos-gluster*-test gdeploy
> > > > >   (test, test, test, ..)
> > > > >
> > > >
> > > > It works, I have testing the install , remove and upgrade. The
> Ansible >
> > > > 2.5 pre requisites needs to
> > > > be take care of.
> > >
> > > Can you explain what you mean to say with this? Is ansible > 2.5 not
> > > availble in the standard repositories and you got the version from
> > > somewhere else?
> > >
> > >
> > Yeah, he was not able to get it from standard repository. User can get
> one
> > from EPEL or other repository.
>
> The content sets from the CentOS SIGs may not rely on 3rd party
> repositories. That means we would have to include ansible 2.5+ somehow
> in our repositories. I need to check how other SIGs do this, and what
> the most suitable way for us is. Until that is resolved, we can't
> release this update yet.
>

Niels, I see a user comment:
https://bugzilla.redhat.com/show_bug.cgi?id=1671559#c5
that they get the Ansible from ovirt repo. Who are the sole consumers of
gdeploy for
setting up RHHI. Is it ok to release the package for their benefit?


> Niels
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190205/a3b4f407/attachment.html>

From ndevos at redhat.com  Tue Feb  5 15:41:37 2019
From: ndevos at redhat.com (Niels de Vos)
Date: Tue, 5 Feb 2019 16:41:37 +0100
Subject: [gluster-packaging] gdeploy-2.0.11 available for testing
In-Reply-To: <CAE44-AvpB8=qeXEESe8zFVC6ABsuv3z_CdEZnL5eDgYurf6vTA@mail.gmail.com>
References: <20190129105614.GC2414@ndevos-x270.lan.nixpanic.net>
	<CAA3LYT+rbNDUUDwiAGuUJxct+CRj7-V4NCZQExBQJi8VJgG_dg@mail.gmail.com>
	<20190131085712.GM2414@ndevos-x270.lan.nixpanic.net>
	<CAE44-AtrMpQDf8XYANu3vp6KJgJHJt+LMbL_+xo1jd8yM2RCLg@mail.gmail.com>
	<20190131113629.GP2414@ndevos-x270.lan.nixpanic.net>
	<CAE44-AvpB8=qeXEESe8zFVC6ABsuv3z_CdEZnL5eDgYurf6vTA@mail.gmail.com>
Message-ID: <20190205154137.GA2877@ndevos-x270>

On Tue, Feb 05, 2019 at 05:01:04PM +0530, Sachidananda URS wrote:
> On Thu, Jan 31, 2019 at 5:06 PM Niels de Vos <ndevos at redhat.com> wrote:
> 
> > On Thu, Jan 31, 2019 at 02:48:13PM +0530, Sachidananda URS wrote:
> > > On Thu, Jan 31, 2019 at 2:27 PM Niels de Vos <ndevos at redhat.com> wrote:
> > >
> > > > On Thu, Jan 31, 2019 at 09:37:15AM +0530, Ramakrishna Reddy Yekulla
> > wrote:
> > > > > On Tue, Jan 29, 2019 at 4:26 PM Niels de Vos <ndevos at redhat.com>
> > wrote:
> > > > >
> > > > > > gdeploy-2.0.11-1.el7 is available in the centos-gluster*-test
> > > > > > repositories from the CentOS Storage SIG. Please test the update
> > and
> > > > let
> > > > > > me know when the package can be marked for release.
> > > > > >
> > > > > >   # yum install centos-release-gluster
> > > > > >   # yum install --enablerepo=centos-gluster*-test gdeploy
> > > > > >   (test, test, test, ..)
> > > > > >
> > > > >
> > > > > It works, I have testing the install , remove and upgrade. The
> > Ansible >
> > > > > 2.5 pre requisites needs to
> > > > > be take care of.
> > > >
> > > > Can you explain what you mean to say with this? Is ansible > 2.5 not
> > > > availble in the standard repositories and you got the version from
> > > > somewhere else?
> > > >
> > > >
> > > Yeah, he was not able to get it from standard repository. User can get
> > one
> > > from EPEL or other repository.
> >
> > The content sets from the CentOS SIGs may not rely on 3rd party
> > repositories. That means we would have to include ansible 2.5+ somehow
> > in our repositories. I need to check how other SIGs do this, and what
> > the most suitable way for us is. Until that is resolved, we can't
> > release this update yet.
> >
> 
> Niels, I see a user comment:
> https://bugzilla.redhat.com/show_bug.cgi?id=1671559#c5
> that they get the Ansible from ovirt repo. Who are the sole consumers of
> gdeploy for
> setting up RHHI. Is it ok to release the package for their benefit?

It is not possible to release the package for a single project, but not
for others. The ansible dependency would still be a problem for all
other users that do not have the ovirt repository enabled.

However oVirt picks gdeploy from the testing repository. So it may get
included in a next oVirt build? Not sure how that works though...

https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;f=hc-basic-suite-master/reposync-config.repo;hb=HEAD#l63

Niels

From surs at redhat.com  Wed Feb  6 04:48:31 2019
From: surs at redhat.com (Sachidananda URS)
Date: Wed, 6 Feb 2019 10:18:31 +0530
Subject: [gluster-packaging] gdeploy-2.0.11 available for testing
In-Reply-To: <20190205154137.GA2877@ndevos-x270>
References: <20190129105614.GC2414@ndevos-x270.lan.nixpanic.net>
	<CAA3LYT+rbNDUUDwiAGuUJxct+CRj7-V4NCZQExBQJi8VJgG_dg@mail.gmail.com>
	<20190131085712.GM2414@ndevos-x270.lan.nixpanic.net>
	<CAE44-AtrMpQDf8XYANu3vp6KJgJHJt+LMbL_+xo1jd8yM2RCLg@mail.gmail.com>
	<20190131113629.GP2414@ndevos-x270.lan.nixpanic.net>
	<CAE44-AvpB8=qeXEESe8zFVC6ABsuv3z_CdEZnL5eDgYurf6vTA@mail.gmail.com>
	<20190205154137.GA2877@ndevos-x270>
Message-ID: <CAE44-Asauk1Mt_DggbmiU2KMvpZc-kaA6JhT7JtM4t3PBtVywg@mail.gmail.com>

On Tue, Feb 5, 2019 at 9:11 PM Niels de Vos <ndevos at redhat.com> wrote:

> On Tue, Feb 05, 2019 at 05:01:04PM +0530, Sachidananda URS wrote:
> > On Thu, Jan 31, 2019 at 5:06 PM Niels de Vos <ndevos at redhat.com> wrote:
> >
> >
> > Niels, I see a user comment:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1671559#c5
> > that they get the Ansible from ovirt repo. Who are the sole consumers of
> > gdeploy for
> > setting up RHHI. Is it ok to release the package for their benefit?
>
> It is not possible to release the package for a single project, but not
> for others. The ansible dependency would still be a problem for all
> other users that do not have the ovirt repository enabled.
>
>
If that is not possible, how can we add latest ansible to CentOS?
What would be the process?


> However oVirt picks gdeploy from the testing repository. So it may get
> included in a next oVirt build? Not sure how that works though...
>
>
> https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;f=hc-basic-suite-master/reposync-config.repo;hb=HEAD#l63


I'm not sure how this works either.


>
> Niels
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190206/70108367/attachment.html>

From srangana at redhat.com  Fri Feb  8 14:55:32 2019
From: srangana at redhat.com (Shyam Ranganathan)
Date: Fri, 8 Feb 2019 09:55:32 -0500
Subject: [gluster-packaging] Release 5.4: Earlier than Mar-10th
Message-ID: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>

Hi,

There have been several crashes and issues reported by users on the
latest 5.3 release. Around 10 patches have been merged since 5.3 and we
have a few more addressing the blockers against 5.4 [1].

The original date was March 10th, but we would like to accelerate a 5.4
release to earlier this month, once all critical blockers are fixed.

Hence there are 3 asks in this mail,

1) Packaging team, would it be possible to accommodate an 5.4 release
around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
we get the required fixes by then.

2) Maintainers, what other issues need to be tracked as blockers? Please
add them to [1].

3) Current blocker status reads as follows:
- Bug 1651246 - Failed to dispatch handler
  - This shows 2 patches that are merged, but there is no patch that
claims this is "Fixed" hence bug is still in POST state. What other
fixes are we expecting on this?
  - @Milind request you to update the status

- Bug 1671556 - glusterfs FUSE client crashing every few days with
'Failed to dispatch handler'
  - Awaiting fixes for identified issues
  - @Nithya what would be the target date?

- Bug 1671603 - flooding of "dict is NULL" logging & crash of client process
  - Awaiting a fix, what is the potential target date for the same?
  - We also need the bug assigned to a person

Thanks,
Shyam

[1] Release 5.4 tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4

From kkeithle at redhat.com  Fri Feb  8 16:18:22 2019
From: kkeithle at redhat.com (Kaleb Keithley)
Date: Fri, 8 Feb 2019 11:18:22 -0500
Subject: [gluster-packaging] Release 5.4: Earlier than Mar-10th
In-Reply-To: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
Message-ID: <CAC+Jd5D8RV03x=WyYXQqkhEgDVsb98UVK8Um5po3ntbNjbPREg@mail.gmail.com>

packages will get built one way or another. :-)

I've mentioned this on numerous occasions but it seems to largely fall on
deaf ears: we need other people to step up and take over some of the burden
of building community packages.  Or we need to cut back on the number of
community packages that we build.

Because $dayjob

On Fri, Feb 8, 2019 at 9:55 AM Shyam Ranganathan <srangana at redhat.com>
wrote:

> Hi,
>
> There have been several crashes and issues reported by users on the
> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
> have a few more addressing the blockers against 5.4 [1].
>
> The original date was March 10th, but we would like to accelerate a 5.4
> release to earlier this month, once all critical blockers are fixed.
>
> Hence there are 3 asks in this mail,
>
> 1) Packaging team, would it be possible to accommodate an 5.4 release
> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
> we get the required fixes by then.
>
> 2) Maintainers, what other issues need to be tracked as blockers? Please
> add them to [1].
>
> 3) Current blocker status reads as follows:
> - Bug 1651246 - Failed to dispatch handler
>   - This shows 2 patches that are merged, but there is no patch that
> claims this is "Fixed" hence bug is still in POST state. What other
> fixes are we expecting on this?
>   - @Milind request you to update the status
>
> - Bug 1671556 - glusterfs FUSE client crashing every few days with
> 'Failed to dispatch handler'
>   - Awaiting fixes for identified issues
>   - @Nithya what would be the target date?
>
> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
> process
>   - Awaiting a fix, what is the potential target date for the same?
>   - We also need the bug assigned to a person
>
> Thanks,
> Shyam
>
> [1] Release 5.4 tracker:
> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> _______________________________________________
> packaging mailing list
> packaging at gluster.org
> https://lists.gluster.org/mailman/listinfo/packaging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190208/3e088ca8/attachment.html>

From nbalacha at redhat.com  Wed Feb 13 08:54:15 2019
From: nbalacha at redhat.com (Nithya Balachandran)
Date: Wed, 13 Feb 2019 14:24:15 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
Message-ID: <CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>

Adding Raghavendra G and Milind who are working on the patches so they can
update on when they should be ready.

On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com> wrote:

> Hi,
>
> There have been several crashes and issues reported by users on the
> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
> have a few more addressing the blockers against 5.4 [1].
>
> The original date was March 10th, but we would like to accelerate a 5.4
> release to earlier this month, once all critical blockers are fixed.
>
> Hence there are 3 asks in this mail,
>
> 1) Packaging team, would it be possible to accommodate an 5.4 release
> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
> we get the required fixes by then.
>
> 2) Maintainers, what other issues need to be tracked as blockers? Please
> add them to [1].
>
> 3) Current blocker status reads as follows:
> - Bug 1651246 - Failed to dispatch handler
>   - This shows 2 patches that are merged, but there is no patch that
> claims this is "Fixed" hence bug is still in POST state. What other
> fixes are we expecting on this?
>   - @Milind request you to update the status
>
> - Bug 1671556 - glusterfs FUSE client crashing every few days with
> 'Failed to dispatch handler'
>   - Awaiting fixes for identified issues
>   - @Nithya what would be the target date?
>
> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
> process
>   - Awaiting a fix, what is the potential target date for the same?
>   - We also need the bug assigned to a person
>
> Thanks,
> Shyam
>
> [1] Release 5.4 tracker:
> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190213/97a474a8/attachment-0001.html>

From rgowdapp at redhat.com  Wed Feb 13 09:09:40 2019
From: rgowdapp at redhat.com (Raghavendra Gowdappa)
Date: Wed, 13 Feb 2019 14:39:40 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
Message-ID: <CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>

On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <nbalacha at redhat.com>
wrote:

> Adding Raghavendra G and Milind who are working on the patches so they can
> update on when they should be ready.
>
> On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com>
> wrote:
>
>> Hi,
>>
>> There have been several crashes and issues reported by users on the
>> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
>> have a few more addressing the blockers against 5.4 [1].
>>
>> The original date was March 10th, but we would like to accelerate a 5.4
>> release to earlier this month, once all critical blockers are fixed.
>>
>> Hence there are 3 asks in this mail,
>>
>> 1) Packaging team, would it be possible to accommodate an 5.4 release
>> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
>> we get the required fixes by then.
>>
>> 2) Maintainers, what other issues need to be tracked as blockers? Please
>> add them to [1].
>>
>> 3) Current blocker status reads as follows:
>> - Bug 1651246 - Failed to dispatch handler
>>   - This shows 2 patches that are merged, but there is no patch that
>> claims this is "Fixed" hence bug is still in POST state. What other
>> fixes are we expecting on this?
>>   - @Milind request you to update the status
>>
>> - Bug 1671556 - glusterfs FUSE client crashing every few days with
>> 'Failed to dispatch handler'
>>   - Awaiting fixes for identified issues
>>   - @Nithya what would be the target date?
>>
>
Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/

waiting on reviews. I am hoping to get this merged by end of this week and
send a backport.


>> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
>> process
>>   - Awaiting a fix, what is the potential target date for the same?
>>   - We also need the bug assigned to a person
>>
>> Thanks,
>> Shyam
>>
>> [1] Release 5.4 tracker:
>> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>> _______________________________________________
>> maintainers mailing list
>> maintainers at gluster.org
>> https://lists.gluster.org/mailman/listinfo/maintainers
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190213/bb27f4f3/attachment-0001.html>

From srangana at redhat.com  Mon Feb 18 15:13:49 2019
From: srangana at redhat.com (Shyam Ranganathan)
Date: Mon, 18 Feb 2019 10:13:49 -0500
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
Message-ID: <e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>

We have more blockers against 5.4 now marked. Would like to ask the list
and understand what we want to get done with by 5.4 and what the
timeline looks like.

The bug list:
https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp

1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
Title: glustereventsd does not start on Ubuntu 16.04 LTS
Assignee: Aravinda
@aravinda can we understand target dates here?

2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
Title: glusterfs FUSE client crashing every few days with 'Failed to
dispatch handler'
Assignee: Nithya (working on Du and Milind)
@du/@milind can we get an update on this bug and how far away we are?

3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
Title: flooding of "dict is NULL" logging & crash of client process
Assignee: None (Amar has most of the comments)
@amar, do we need 2 bugs here? Also, how far away is a fix?

4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
Title: glusterfs FUSE client crashing every few days with 'Failed to
dispatch handler'
Assignee: Du
@du, we are still waiting to get
https://review.gluster.org/c/glusterfs/+/22189 merged, right?

Shyam
On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
> 
> 
> On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <nbalacha at redhat.com
> <mailto:nbalacha at redhat.com>> wrote:
> 
>     Adding Raghavendra G and Milind who are working on the patches so
>     they can update on when they should be ready.
> 
>     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com
>     <mailto:srangana at redhat.com>> wrote:
> 
>         Hi,
> 
>         There have been several crashes and issues reported by users on the
>         latest 5.3 release. Around 10 patches have been merged since 5.3
>         and we
>         have a few more addressing the blockers against 5.4 [1].
> 
>         The original date was March 10th, but we would like to
>         accelerate a 5.4
>         release to earlier this month, once all critical blockers are fixed.
> 
>         Hence there are 3 asks in this mail,
> 
>         1) Packaging team, would it be possible to accommodate an 5.4
>         release
>         around mid-next week (RC0 for rel-6 is also on the same week)?
>         Assuming
>         we get the required fixes by then.
> 
>         2) Maintainers, what other issues need to be tracked as
>         blockers? Please
>         add them to [1].
> 
>         3) Current blocker status reads as follows:
>         - Bug 1651246 - Failed to dispatch handler
>         ? - This shows 2 patches that are merged, but there is no patch that
>         claims this is "Fixed" hence bug is still in POST state. What other
>         fixes are we expecting on this?
>         ? - @Milind request you to update the status
> 
>         - Bug 1671556 - glusterfs FUSE client crashing every few days with
>         'Failed to dispatch handler'
>         ? - Awaiting fixes for identified issues
>         ? - @Nithya what would be the target date?
> 
> 
> Fix?@ https://review.gluster.org/#/c/glusterfs/+/22189/
> 
> waiting on reviews. I am hoping to get this merged by end of this week
> and send a backport.
> 
> 
>         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
>         client process
>         ? - Awaiting a fix, what is the potential target date for the same?
>         ? - We also need the bug assigned to a person
> 
>         Thanks,
>         Shyam
> 
>         [1] Release 5.4 tracker:
>         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>         _______________________________________________
>         maintainers mailing list
>         maintainers at gluster.org <mailto:maintainers at gluster.org>
>         https://lists.gluster.org/mailman/listinfo/maintainers
> 

From rgowdapp at redhat.com  Tue Feb 19 00:54:04 2019
From: rgowdapp at redhat.com (Raghavendra Gowdappa)
Date: Tue, 19 Feb 2019 06:24:04 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
	<e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
Message-ID: <CAFkORY9jWhH7PhteBbRWcp=1DREUma=LCFJN+94Ym0DPN5TB8A@mail.gmail.com>

On Mon, Feb 18, 2019 at 8:43 PM Shyam Ranganathan <srangana at redhat.com>
wrote:

> We have more blockers against 5.4 now marked. Would like to ask the list
> and understand what we want to get done with by 5.4 and what the
> timeline looks like.
>
> The bug list:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp
>
> 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> Title: glustereventsd does not start on Ubuntu 16.04 LTS
> Assignee: Aravinda
> @aravinda can we understand target dates here?
>
> 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> Assignee: Nithya (working on Du and Milind)
> @du/@milind can we get an update on this bug and how far away we are?
>
> 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> Title: flooding of "dict is NULL" logging & crash of client process
> Assignee: None (Amar has most of the comments)
> @amar, do we need 2 bugs here? Also, how far away is a fix?
>
> 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
> Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> Assignee: Du
> @du, we are still waiting to get
> https://review.gluster.org/c/glusterfs/+/22189 merged, right?
>

Yes. I'll be refreshing the patch today.


> Shyam
> On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
> >
> >
> > On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <nbalacha at redhat.com
> > <mailto:nbalacha at redhat.com>> wrote:
> >
> >     Adding Raghavendra G and Milind who are working on the patches so
> >     they can update on when they should be ready.
> >
> >     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com
> >     <mailto:srangana at redhat.com>> wrote:
> >
> >         Hi,
> >
> >         There have been several crashes and issues reported by users on
> the
> >         latest 5.3 release. Around 10 patches have been merged since 5.3
> >         and we
> >         have a few more addressing the blockers against 5.4 [1].
> >
> >         The original date was March 10th, but we would like to
> >         accelerate a 5.4
> >         release to earlier this month, once all critical blockers are
> fixed.
> >
> >         Hence there are 3 asks in this mail,
> >
> >         1) Packaging team, would it be possible to accommodate an 5.4
> >         release
> >         around mid-next week (RC0 for rel-6 is also on the same week)?
> >         Assuming
> >         we get the required fixes by then.
> >
> >         2) Maintainers, what other issues need to be tracked as
> >         blockers? Please
> >         add them to [1].
> >
> >         3) Current blocker status reads as follows:
> >         - Bug 1651246 - Failed to dispatch handler
> >           - This shows 2 patches that are merged, but there is no patch
> that
> >         claims this is "Fixed" hence bug is still in POST state. What
> other
> >         fixes are we expecting on this?
> >           - @Milind request you to update the status
> >
> >         - Bug 1671556 - glusterfs FUSE client crashing every few days
> with
> >         'Failed to dispatch handler'
> >           - Awaiting fixes for identified issues
> >           - @Nithya what would be the target date?
> >
> >
> > Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/
> >
> > waiting on reviews. I am hoping to get this merged by end of this week
> > and send a backport.
> >
> >
> >         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
> >         client process
> >           - Awaiting a fix, what is the potential target date for the
> same?
> >           - We also need the bug assigned to a person
> >
> >         Thanks,
> >         Shyam
> >
> >         [1] Release 5.4 tracker:
> >         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> >         _______________________________________________
> >         maintainers mailing list
> >         maintainers at gluster.org <mailto:maintainers at gluster.org>
> >         https://lists.gluster.org/mailman/listinfo/maintainers
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190219/bafae00d/attachment-0001.html>

From rgowdapp at redhat.com  Tue Feb 19 02:20:15 2019
From: rgowdapp at redhat.com (Raghavendra Gowdappa)
Date: Tue, 19 Feb 2019 07:50:15 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
	<e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
Message-ID: <CAFkORY9FbHcCoOUWeoGNYjQ+8BJTxa=3hfFCivVF9GHXZzgBQw@mail.gmail.com>

On Mon, Feb 18, 2019 at 8:43 PM Shyam Ranganathan <srangana at redhat.com>
wrote:

> We have more blockers against 5.4 now marked. Would like to ask the list
> and understand what we want to get done with by 5.4 and what the
> timeline looks like.
>
> The bug list:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp
>
> 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> Title: glustereventsd does not start on Ubuntu 16.04 LTS
> Assignee: Aravinda
> @aravinda can we understand target dates here?
>
> 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> Assignee: Nithya (working on Du and Milind)
> @du/@milind can we get an update on this bug and how far away we are?
>

Milind identified as the msg was introduced by coverty fixes -
https://review.gluster.org/#/c/glusterfs/+/20758/. He also has sent a fix
at https://review.gluster.org/#/c/glusterfs/+/22221/, which is merged on
master.


> 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> Title: flooding of "dict is NULL" logging & crash of client process
> Assignee: None (Amar has most of the comments)
> @amar, do we need 2 bugs here? Also, how far away is a fix?
>
> 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
> Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> Assignee: Du
> @du, we are still waiting to get
> https://review.gluster.org/c/glusterfs/+/22189 merged, right?
>
> Shyam
> On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
> >
> >
> > On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <nbalacha at redhat.com
> > <mailto:nbalacha at redhat.com>> wrote:
> >
> >     Adding Raghavendra G and Milind who are working on the patches so
> >     they can update on when they should be ready.
> >
> >     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com
> >     <mailto:srangana at redhat.com>> wrote:
> >
> >         Hi,
> >
> >         There have been several crashes and issues reported by users on
> the
> >         latest 5.3 release. Around 10 patches have been merged since 5.3
> >         and we
> >         have a few more addressing the blockers against 5.4 [1].
> >
> >         The original date was March 10th, but we would like to
> >         accelerate a 5.4
> >         release to earlier this month, once all critical blockers are
> fixed.
> >
> >         Hence there are 3 asks in this mail,
> >
> >         1) Packaging team, would it be possible to accommodate an 5.4
> >         release
> >         around mid-next week (RC0 for rel-6 is also on the same week)?
> >         Assuming
> >         we get the required fixes by then.
> >
> >         2) Maintainers, what other issues need to be tracked as
> >         blockers? Please
> >         add them to [1].
> >
> >         3) Current blocker status reads as follows:
> >         - Bug 1651246 - Failed to dispatch handler
> >           - This shows 2 patches that are merged, but there is no patch
> that
> >         claims this is "Fixed" hence bug is still in POST state. What
> other
> >         fixes are we expecting on this?
> >           - @Milind request you to update the status
> >
> >         - Bug 1671556 - glusterfs FUSE client crashing every few days
> with
> >         'Failed to dispatch handler'
> >           - Awaiting fixes for identified issues
> >           - @Nithya what would be the target date?
> >
> >
> > Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/
> >
> > waiting on reviews. I am hoping to get this merged by end of this week
> > and send a backport.
> >
> >
> >         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
> >         client process
> >           - Awaiting a fix, what is the potential target date for the
> same?
> >           - We also need the bug assigned to a person
> >
> >         Thanks,
> >         Shyam
> >
> >         [1] Release 5.4 tracker:
> >         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> >         _______________________________________________
> >         maintainers mailing list
> >         maintainers at gluster.org <mailto:maintainers at gluster.org>
> >         https://lists.gluster.org/mailman/listinfo/maintainers
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190219/4c0dfda9/attachment-0001.html>

From jenkins at build.gluster.org  Fri Feb 22 04:15:39 2019
From: jenkins at build.gluster.org (jenkins at build.gluster.org)
Date: Fri, 22 Feb 2019 04:15:39 +0000 (UTC)
Subject: [gluster-packaging] glusterfs-6.0rc0 released
Message-ID: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>

SRC: https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.tar.gz
HASH: https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.sha512sum

This release is made off jenkins-release-79

From ndevos at redhat.com  Fri Feb 22 13:51:53 2019
From: ndevos at redhat.com (Niels de Vos)
Date: Fri, 22 Feb 2019 14:51:53 +0100
Subject: [gluster-packaging] [Gluster-Maintainers] glusterfs-6.0rc0
	released
In-Reply-To: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
References: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
Message-ID: <20190222135153.GE2496@ndevos-x270>

On Fri, Feb 22, 2019 at 04:15:39AM +0000, jenkins at build.gluster.org wrote:
> SRC: https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.tar.gz
> HASH: https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.sha512sum

When will the tarball land under
https://download.gluster.org/pub/gluster/glusterfs/6 ?

I'll try to get the builds done today or over the weekend. The CentOS
team will need to setup the sync from the buildsystem to the standard
repository locations once the builds are available. Once its done, I'll
let everyone know.

Niels

From kkeithle at redhat.com  Fri Feb 22 15:37:19 2019
From: kkeithle at redhat.com (Kaleb Keithley)
Date: Fri, 22 Feb 2019 10:37:19 -0500
Subject: [gluster-packaging] [Gluster-Maintainers] glusterfs-6.0rc0
	released
In-Reply-To: <20190222135153.GE2496@ndevos-x270>
References: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
	<20190222135153.GE2496@ndevos-x270>
Message-ID: <CAC+Jd5C4CLUVA4EsgyZTPD14qxCLsa9GCi=50XrLqfrmeWkghQ@mail.gmail.com>

RCs have always landed at
https://download.gluster.org/pub/gluster/glusterfs/qa-releases/

RC0  is at
https://download.gluster.org/pub/gluster/glusterfs/qa-releases/6.0rc0/glusterfs-6.0rc0.tar.gz

On Fri, Feb 22, 2019 at 8:52 AM Niels de Vos <ndevos at redhat.com> wrote:

> On Fri, Feb 22, 2019 at 04:15:39AM +0000, jenkins at build.gluster.org wrote:
> > SRC:
> https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.tar.gz
> > HASH:
> https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.sha512sum
>
> When will the tarball land under
> https://download.gluster.org/pub/gluster/glusterfs/6 ?
>
> I'll try to get the builds done today or over the weekend. The CentOS
> team will need to setup the sync from the buildsystem to the standard
> repository locations once the builds are available. Once its done, I'll
> let everyone know.
>
> Niels
> _______________________________________________
> packaging mailing list
> packaging at gluster.org
> https://lists.gluster.org/mailman/listinfo/packaging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190222/fe136f63/attachment.html>

From kkeithle at redhat.com  Sat Feb 23 14:41:41 2019
From: kkeithle at redhat.com (Kaleb Keithley)
Date: Sat, 23 Feb 2019 15:41:41 +0100
Subject: [gluster-packaging] [Gluster-Maintainers] glusterfs-6.0rc0
	released
In-Reply-To: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
References: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
Message-ID: <CAC+Jd5CHffH87oBCo+c0PvN085f4ezA6W=Zx6JdjQHw_okXO3g@mail.gmail.com>

GlusterFS 6.0rc0 is built in Fedora 30 and Fedora 31/rawhide.

Packages for Fedora 29, RHEL 8, RHEL 7, and RHEL 6* and Debian 9/stretch
and Debian 10/buster are at
https://download.gluster.org/pub/gluster/glusterfs/qa-releases/6.0rc0/

Packages are signed. The public key is at
https://download.gluster.org/pub/gluster/glusterfs/6/rsa.pub

* RHEL 6 is client-side only. Fedora 29, RHEL 7, and RHEL 6 RPMs are Fedora
Koji scratch builds. RHEL 7 and RHEL 6 RPMs are provided here for
convenience only, and are independent of the RPMs in the CentOS Storage SIG.

On Fri, Feb 22, 2019 at 5:16 AM <jenkins at build.gluster.org> wrote:

> SRC:
> https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.tar.gz
> HASH:
> https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.sha512sum
>
> This release is made off
> jenkins-release-79_______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190223/7d7b0363/attachment.html>

From srangana at redhat.com  Mon Feb 25 15:42:01 2019
From: srangana at redhat.com (Shyam Ranganathan)
Date: Mon, 25 Feb 2019 10:42:01 -0500
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
	<e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
Message-ID: <4ebfb6a7-52de-baf7-dfe9-d8e89344fbd4@redhat.com>

Time to reset and understand where we are at here. The dates are
slipping, but the tracker is still having the following blockers.

We need to either understand when these would be fixed, and take a call
on creating 5.4 with known issues not addressed in the blocker, or wait
for the fixes. Responses to the bugs and updates to bugzilla would help
deciding on the same.

1) Title: glustereventsd does not start on Ubuntu 16.04 LTS
https://bugzilla.redhat.com/show_bug.cgi?id=1649054

@aravinda, any updates? Should we wait, of will this take more time?

2) Title: glusterfs FUSE client crashing every few days with 'Failed to
dispatch handler'
https://bugzilla.redhat.com/show_bug.cgi?id=1671556

All patches against the bug are merged, but bug remains in POST state,
as none of the patches claim that the issue "Fixes" the reported problem.

Are we awaiting more patches for the same? Du/Milind/Nithya?

3) Title: flooding of "dict is NULL" logging & crash of client process
https://bugzilla.redhat.com/show_bug.cgi?id=1671603

Still in NEW state, Du/Amar, do we have a date for resolution?

Thanks,
Shyam
On 2/18/19 10:13 AM, Shyam Ranganathan wrote:
> We have more blockers against 5.4 now marked. Would like to ask the list
> and understand what we want to get done with by 5.4 and what the
> timeline looks like.
> 
> The bug list:
> https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp
> 
> 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> Title: glustereventsd does not start on Ubuntu 16.04 LTS
> Assignee: Aravinda
> @aravinda can we understand target dates here?
> 
> 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> Assignee: Nithya (working on Du and Milind)
> @du/@milind can we get an update on this bug and how far away we are?
> 
> 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> Title: flooding of "dict is NULL" logging & crash of client process
> Assignee: None (Amar has most of the comments)
> @amar, do we need 2 bugs here? Also, how far away is a fix?
> 
> 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
> Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> Assignee: Du
> @du, we are still waiting to get
> https://review.gluster.org/c/glusterfs/+/22189 merged, right?
> 
> Shyam
> On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
>>
>>
>> On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <nbalacha at redhat.com
>> <mailto:nbalacha at redhat.com>> wrote:
>>
>>     Adding Raghavendra G and Milind who are working on the patches so
>>     they can update on when they should be ready.
>>
>>     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com
>>     <mailto:srangana at redhat.com>> wrote:
>>
>>         Hi,
>>
>>         There have been several crashes and issues reported by users on the
>>         latest 5.3 release. Around 10 patches have been merged since 5.3
>>         and we
>>         have a few more addressing the blockers against 5.4 [1].
>>
>>         The original date was March 10th, but we would like to
>>         accelerate a 5.4
>>         release to earlier this month, once all critical blockers are fixed.
>>
>>         Hence there are 3 asks in this mail,
>>
>>         1) Packaging team, would it be possible to accommodate an 5.4
>>         release
>>         around mid-next week (RC0 for rel-6 is also on the same week)?
>>         Assuming
>>         we get the required fixes by then.
>>
>>         2) Maintainers, what other issues need to be tracked as
>>         blockers? Please
>>         add them to [1].
>>
>>         3) Current blocker status reads as follows:
>>         - Bug 1651246 - Failed to dispatch handler
>>         ? - This shows 2 patches that are merged, but there is no patch that
>>         claims this is "Fixed" hence bug is still in POST state. What other
>>         fixes are we expecting on this?
>>         ? - @Milind request you to update the status
>>
>>         - Bug 1671556 - glusterfs FUSE client crashing every few days with
>>         'Failed to dispatch handler'
>>         ? - Awaiting fixes for identified issues
>>         ? - @Nithya what would be the target date?
>>
>>
>> Fix?@ https://review.gluster.org/#/c/glusterfs/+/22189/
>>
>> waiting on reviews. I am hoping to get this merged by end of this week
>> and send a backport.
>>
>>
>>         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
>>         client process
>>         ? - Awaiting a fix, what is the potential target date for the same?
>>         ? - We also need the bug assigned to a person
>>
>>         Thanks,
>>         Shyam
>>
>>         [1] Release 5.4 tracker:
>>         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>>         _______________________________________________
>>         maintainers mailing list
>>         maintainers at gluster.org <mailto:maintainers at gluster.org>
>>         https://lists.gluster.org/mailman/listinfo/maintainers
>>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
> 

From nbalacha at redhat.com  Mon Feb 25 16:00:18 2019
From: nbalacha at redhat.com (Nithya Balachandran)
Date: Mon, 25 Feb 2019 21:30:18 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <4ebfb6a7-52de-baf7-dfe9-d8e89344fbd4@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
	<e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
	<4ebfb6a7-52de-baf7-dfe9-d8e89344fbd4@redhat.com>
Message-ID: <CAOUCJ=j8bx1rZ5gaDxTCyCTqZDAXyqicLR0g+7nzdwj0-sz8Xg@mail.gmail.com>

On Mon, 25 Feb 2019 at 21:12, Shyam Ranganathan <srangana at redhat.com> wrote:

> Time to reset and understand where we are at here. The dates are
> slipping, but the tracker is still having the following blockers.
>
> We need to either understand when these would be fixed, and take a call
> on creating 5.4 with known issues not addressed in the blocker, or wait
> for the fixes. Responses to the bugs and updates to bugzilla would help
> deciding on the same.
>
> 1) Title: glustereventsd does not start on Ubuntu 16.04 LTS
> https://bugzilla.redhat.com/show_bug.cgi?id=1649054
>
> @aravinda, any updates? Should we wait, of will this take more time?
>
> IMO, this is not a prio for the interim release as the main focus is the
log floods and crashes which are affecting production for a lot of users.
Can this go into the next release?


> 2) Title: glusterfs FUSE client crashing every few days with 'Failed to
> dispatch handler'
> https://bugzilla.redhat.com/show_bug.cgi?id=1671556
>
> All patches against the bug are merged, but bug remains in POST state,
> as none of the patches claim that the issue "Fixes" the reported problem.
>
> Are we awaiting more patches for the same? Du/Milind/Nithya?
>

The crash fixes - this should do for the moment though one user has
reported a crash even after turning off wb. IMO, we should go ahead with
what we have. @Raghavendra Gowdappa <rgowdapp at redhat.com> , what do you
think?


>
> 3) Title: flooding of "dict is NULL" logging & crash of client process
> https://bugzilla.redhat.com/show_bug.cgi?id=1671603
>
> Still in NEW state, Du/Amar, do we have a date for resolution?
>
> Thanks,
> Shyam
> On 2/18/19 10:13 AM, Shyam Ranganathan wrote:
> > We have more blockers against 5.4 now marked. Would like to ask the list
> > and understand what we want to get done with by 5.4 and what the
> > timeline looks like.
> >
> > The bug list:
> >
> https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp
> >
> > 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> > Title: glustereventsd does not start on Ubuntu 16.04 LTS
> > Assignee: Aravinda
> > @aravinda can we understand target dates here?
> >
> > 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> > Title: glusterfs FUSE client crashing every few days with 'Failed to
> > dispatch handler'
> > Assignee: Nithya (working on Du and Milind)
> > @du/@milind can we get an update on this bug and how far away we are?
> >
> > 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> > Title: flooding of "dict is NULL" logging & crash of client process
> > Assignee: None (Amar has most of the comments)
> > @amar, do we need 2 bugs here? Also, how far away is a fix?
> >
> > 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
> > Title: glusterfs FUSE client crashing every few days with 'Failed to
> > dispatch handler'
> > Assignee: Du
> > @du, we are still waiting to get
> > https://review.gluster.org/c/glusterfs/+/22189 merged, right?
> >
> > Shyam
> > On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
> >>
> >>
> >> On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <
> nbalacha at redhat.com
> >> <mailto:nbalacha at redhat.com>> wrote:
> >>
> >>     Adding Raghavendra G and Milind who are working on the patches so
> >>     they can update on when they should be ready.
> >>
> >>     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <srangana at redhat.com
> >>     <mailto:srangana at redhat.com>> wrote:
> >>
> >>         Hi,
> >>
> >>         There have been several crashes and issues reported by users on
> the
> >>         latest 5.3 release. Around 10 patches have been merged since 5.3
> >>         and we
> >>         have a few more addressing the blockers against 5.4 [1].
> >>
> >>         The original date was March 10th, but we would like to
> >>         accelerate a 5.4
> >>         release to earlier this month, once all critical blockers are
> fixed.
> >>
> >>         Hence there are 3 asks in this mail,
> >>
> >>         1) Packaging team, would it be possible to accommodate an 5.4
> >>         release
> >>         around mid-next week (RC0 for rel-6 is also on the same week)?
> >>         Assuming
> >>         we get the required fixes by then.
> >>
> >>         2) Maintainers, what other issues need to be tracked as
> >>         blockers? Please
> >>         add them to [1].
> >>
> >>         3) Current blocker status reads as follows:
> >>         - Bug 1651246 - Failed to dispatch handler
> >>           - This shows 2 patches that are merged, but there is no patch
> that
> >>         claims this is "Fixed" hence bug is still in POST state. What
> other
> >>         fixes are we expecting on this?
> >>           - @Milind request you to update the status
> >>
> >>         - Bug 1671556 - glusterfs FUSE client crashing every few days
> with
> >>         'Failed to dispatch handler'
> >>           - Awaiting fixes for identified issues
> >>           - @Nithya what would be the target date?
> >>
> >>
> >> Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/
> >>
> >> waiting on reviews. I am hoping to get this merged by end of this week
> >> and send a backport.
> >>
> >>
> >>         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
> >>         client process
> >>           - Awaiting a fix, what is the potential target date for the
> same?
> >>           - We also need the bug assigned to a person
> >>
> >>         Thanks,
> >>         Shyam
> >>
> >>         [1] Release 5.4 tracker:
> >>         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> >>         _______________________________________________
> >>         maintainers mailing list
> >>         maintainers at gluster.org <mailto:maintainers at gluster.org>
> >>         https://lists.gluster.org/mailman/listinfo/maintainers
> >>
> > _______________________________________________
> > maintainers mailing list
> > maintainers at gluster.org
> > https://lists.gluster.org/mailman/listinfo/maintainers
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190225/a5c1b4f3/attachment-0001.html>

From rgowdapp at redhat.com  Mon Feb 25 16:04:24 2019
From: rgowdapp at redhat.com (Raghavendra Gowdappa)
Date: Mon, 25 Feb 2019 21:34:24 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <CAOUCJ=j8bx1rZ5gaDxTCyCTqZDAXyqicLR0g+7nzdwj0-sz8Xg@mail.gmail.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
	<e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
	<4ebfb6a7-52de-baf7-dfe9-d8e89344fbd4@redhat.com>
	<CAOUCJ=j8bx1rZ5gaDxTCyCTqZDAXyqicLR0g+7nzdwj0-sz8Xg@mail.gmail.com>
Message-ID: <CAFkORY_NGvG1qzQOrX6Y1GTrrsCuc_3ms8yiCwp9uEyPqMbnFQ@mail.gmail.com>

On Mon, Feb 25, 2019 at 9:30 PM Nithya Balachandran <nbalacha at redhat.com>
wrote:

>
>
> On Mon, 25 Feb 2019 at 21:12, Shyam Ranganathan <srangana at redhat.com>
> wrote:
>
>> Time to reset and understand where we are at here. The dates are
>> slipping, but the tracker is still having the following blockers.
>>
>> We need to either understand when these would be fixed, and take a call
>> on creating 5.4 with known issues not addressed in the blocker, or wait
>> for the fixes. Responses to the bugs and updates to bugzilla would help
>> deciding on the same.
>>
>> 1) Title: glustereventsd does not start on Ubuntu 16.04 LTS
>> https://bugzilla.redhat.com/show_bug.cgi?id=1649054
>>
>> @aravinda, any updates? Should we wait, of will this take more time?
>>
>> IMO, this is not a prio for the interim release as the main focus is the
> log floods and crashes which are affecting production for a lot of users.
> Can this go into the next release?
>
>
>> 2) Title: glusterfs FUSE client crashing every few days with 'Failed to
>> dispatch handler'
>> https://bugzilla.redhat.com/show_bug.cgi?id=1671556
>>
>> All patches against the bug are merged, but bug remains in POST state,
>> as none of the patches claim that the issue "Fixes" the reported problem.
>>
>> Are we awaiting more patches for the same? Du/Milind/Nithya?
>>
>
> The crash fixes - this should do for the moment though one user has
> reported a crash even after turning off wb. IMO, we should go ahead with
> what we have. @Raghavendra Gowdappa <rgowdapp at redhat.com> , what do you
> think?
>

Yes. Actually  https://review.gluster.org/#/c/glusterfs/+/22231/ says
"Fixes", but I think its made dependent on another patch which says
"updates". The dependency order should've been other way. This might be the
reason why bug state is not changed.


>
>>
>> 3) Title: flooding of "dict is NULL" logging & crash of client process
>> https://bugzilla.redhat.com/show_bug.cgi?id=1671603
>>
>> Still in NEW state, Du/Amar, do we have a date for resolution?
>>
>> Thanks,
>> Shyam
>> On 2/18/19 10:13 AM, Shyam Ranganathan wrote:
>> > We have more blockers against 5.4 now marked. Would like to ask the list
>> > and understand what we want to get done with by 5.4 and what the
>> > timeline looks like.
>> >
>> > The bug list:
>> >
>> https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp
>> >
>> > 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
>> > Title: glustereventsd does not start on Ubuntu 16.04 LTS
>> > Assignee: Aravinda
>> > @aravinda can we understand target dates here?
>> >
>> > 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
>> > Title: glusterfs FUSE client crashing every few days with 'Failed to
>> > dispatch handler'
>> > Assignee: Nithya (working on Du and Milind)
>> > @du/@milind can we get an update on this bug and how far away we are?
>> >
>> > 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
>> > Title: flooding of "dict is NULL" logging & crash of client process
>> > Assignee: None (Amar has most of the comments)
>> > @amar, do we need 2 bugs here? Also, how far away is a fix?
>> >
>> > 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
>> > Title: glusterfs FUSE client crashing every few days with 'Failed to
>> > dispatch handler'
>> > Assignee: Du
>> > @du, we are still waiting to get
>> > https://review.gluster.org/c/glusterfs/+/22189 merged, right?
>> >
>> > Shyam
>> > On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
>> >>
>> >>
>> >> On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <
>> nbalacha at redhat.com
>> >> <mailto:nbalacha at redhat.com>> wrote:
>> >>
>> >>     Adding Raghavendra G and Milind who are working on the patches so
>> >>     they can update on when they should be ready.
>> >>
>> >>     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <
>> srangana at redhat.com
>> >>     <mailto:srangana at redhat.com>> wrote:
>> >>
>> >>         Hi,
>> >>
>> >>         There have been several crashes and issues reported by users
>> on the
>> >>         latest 5.3 release. Around 10 patches have been merged since
>> 5.3
>> >>         and we
>> >>         have a few more addressing the blockers against 5.4 [1].
>> >>
>> >>         The original date was March 10th, but we would like to
>> >>         accelerate a 5.4
>> >>         release to earlier this month, once all critical blockers are
>> fixed.
>> >>
>> >>         Hence there are 3 asks in this mail,
>> >>
>> >>         1) Packaging team, would it be possible to accommodate an 5.4
>> >>         release
>> >>         around mid-next week (RC0 for rel-6 is also on the same week)?
>> >>         Assuming
>> >>         we get the required fixes by then.
>> >>
>> >>         2) Maintainers, what other issues need to be tracked as
>> >>         blockers? Please
>> >>         add them to [1].
>> >>
>> >>         3) Current blocker status reads as follows:
>> >>         - Bug 1651246 - Failed to dispatch handler
>> >>           - This shows 2 patches that are merged, but there is no
>> patch that
>> >>         claims this is "Fixed" hence bug is still in POST state. What
>> other
>> >>         fixes are we expecting on this?
>> >>           - @Milind request you to update the status
>> >>
>> >>         - Bug 1671556 - glusterfs FUSE client crashing every few days
>> with
>> >>         'Failed to dispatch handler'
>> >>           - Awaiting fixes for identified issues
>> >>           - @Nithya what would be the target date?
>> >>
>> >>
>> >> Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/
>> >>
>> >> waiting on reviews. I am hoping to get this merged by end of this week
>> >> and send a backport.
>> >>
>> >>
>> >>         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
>> >>         client process
>> >>           - Awaiting a fix, what is the potential target date for the
>> same?
>> >>           - We also need the bug assigned to a person
>> >>
>> >>         Thanks,
>> >>         Shyam
>> >>
>> >>         [1] Release 5.4 tracker:
>> >>         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>> >>         _______________________________________________
>> >>         maintainers mailing list
>> >>         maintainers at gluster.org <mailto:maintainers at gluster.org>
>> >>         https://lists.gluster.org/mailman/listinfo/maintainers
>> >>
>> > _______________________________________________
>> > maintainers mailing list
>> > maintainers at gluster.org
>> > https://lists.gluster.org/mailman/listinfo/maintainers
>> >
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190225/d008dbdf/attachment.html>

From avishwan at redhat.com  Tue Feb 26 11:17:38 2019
From: avishwan at redhat.com (Aravinda)
Date: Tue, 26 Feb 2019 16:47:38 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <4ebfb6a7-52de-baf7-dfe9-d8e89344fbd4@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAOUCJ=gdS=zmiGfWKO54BkQxQV1U80NjyoaGaoi16iDRgw5=fQ@mail.gmail.com>
	<CAFkORY99SCpPppP5BNDMa-kh7SUg7r7rUBubmkDL5h_JzK-uzQ@mail.gmail.com>
	<e2c6e43a-ba54-f721-6d7c-9cf4b1e42066@redhat.com>
	<4ebfb6a7-52de-baf7-dfe9-d8e89344fbd4@redhat.com>
Message-ID: <6f0612b786528c0d3dd38af58e1679659b381899.camel@redhat.com>

On Mon, 2019-02-25 at 10:42 -0500, Shyam Ranganathan wrote:
> Time to reset and understand where we are at here. The dates are
> slipping, but the tracker is still having the following blockers.
> 
> We need to either understand when these would be fixed, and take a
> call
> on creating 5.4 with known issues not addressed in the blocker, or
> wait
> for the fixes. Responses to the bugs and updates to bugzilla would
> help
> deciding on the same.
> 
> 1) Title: glustereventsd does not start on Ubuntu 16.04 LTS
> https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> 
> @aravinda, any updates? Should we wait, of will this take more time?

Patch merged in master and release-5 Patch yet to be merged
https://review.gluster.org/#/c/glusterfs/+/22262/

> 
> 2) Title: glusterfs FUSE client crashing every few days with 'Failed
> to
> dispatch handler'
> https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> 
> All patches against the bug are merged, but bug remains in POST
> state,
> as none of the patches claim that the issue "Fixes" the reported
> problem.
> 
> Are we awaiting more patches for the same? Du/Milind/Nithya?
> 
> 3) Title: flooding of "dict is NULL" logging & crash of client
> process
> https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> 
> Still in NEW state, Du/Amar, do we have a date for resolution?
> 
> Thanks,
> Shyam
> On 2/18/19 10:13 AM, Shyam Ranganathan wrote:
> > We have more blockers against 5.4 now marked. Would like to ask the
> > list
> > and understand what we want to get done with by 5.4 and what the
> > timeline looks like.
> > 
> > The bug list:
> > https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp
> > 
> > 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> > Title: glustereventsd does not start on Ubuntu 16.04 LTS
> > Assignee: Aravinda
> > @aravinda can we understand target dates here?
> > 
> > 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> > Title: glusterfs FUSE client crashing every few days with 'Failed
> > to
> > dispatch handler'
> > Assignee: Nithya (working on Du and Milind)
> > @du/@milind can we get an update on this bug and how far away we
> > are?
> > 
> > 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> > Title: flooding of "dict is NULL" logging & crash of client process
> > Assignee: None (Amar has most of the comments)
> > @amar, do we need 2 bugs here? Also, how far away is a fix?
> > 
> > 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
> > Title: glusterfs FUSE client crashing every few days with 'Failed
> > to
> > dispatch handler'
> > Assignee: Du
> > @du, we are still waiting to get
> > https://review.gluster.org/c/glusterfs/+/22189 merged, right?
> > 
> > Shyam
> > On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
> > > 
> > > On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <
> > > nbalacha at redhat.com
> > > <mailto:nbalacha at redhat.com>> wrote:
> > > 
> > >     Adding Raghavendra G and Milind who are working on the
> > > patches so
> > >     they can update on when they should be ready.
> > > 
> > >     On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <
> > > srangana at redhat.com
> > >     <mailto:srangana at redhat.com>> wrote:
> > > 
> > >         Hi,
> > > 
> > >         There have been several crashes and issues reported by
> > > users on the
> > >         latest 5.3 release. Around 10 patches have been merged
> > > since 5.3
> > >         and we
> > >         have a few more addressing the blockers against 5.4 [1].
> > > 
> > >         The original date was March 10th, but we would like to
> > >         accelerate a 5.4
> > >         release to earlier this month, once all critical blockers
> > > are fixed.
> > > 
> > >         Hence there are 3 asks in this mail,
> > > 
> > >         1) Packaging team, would it be possible to accommodate an
> > > 5.4
> > >         release
> > >         around mid-next week (RC0 for rel-6 is also on the same
> > > week)?
> > >         Assuming
> > >         we get the required fixes by then.
> > > 
> > >         2) Maintainers, what other issues need to be tracked as
> > >         blockers? Please
> > >         add them to [1].
> > > 
> > >         3) Current blocker status reads as follows:
> > >         - Bug 1651246 - Failed to dispatch handler
> > >           - This shows 2 patches that are merged, but there is no
> > > patch that
> > >         claims this is "Fixed" hence bug is still in POST state.
> > > What other
> > >         fixes are we expecting on this?
> > >           - @Milind request you to update the status
> > > 
> > >         - Bug 1671556 - glusterfs FUSE client crashing every few
> > > days with
> > >         'Failed to dispatch handler'
> > >           - Awaiting fixes for identified issues
> > >           - @Nithya what would be the target date?
> > > 
> > > 
> > > Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/
> > > 
> > > waiting on reviews. I am hoping to get this merged by end of this
> > > week
> > > and send a backport.
> > > 
> > > 
> > >         - Bug 1671603 - flooding of "dict is NULL" logging &
> > > crash of
> > >         client process
> > >           - Awaiting a fix, what is the potential target date for
> > > the same?
> > >           - We also need the bug assigned to a person
> > > 
> > >         Thanks,
> > >         Shyam
> > > 
> > >         [1] Release 5.4 tracker:
> > >         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> > >         _______________________________________________
> > >         maintainers mailing list
> > >         maintainers at gluster.org <mailto:maintainers at gluster.org>
> > >         https://lists.gluster.org/mailman/listinfo/maintainers
> > > 
> > _______________________________________________
> > maintainers mailing list
> > maintainers at gluster.org
> > https://lists.gluster.org/mailman/listinfo/maintainers
> > 
-- 
regards
Aravinda


From mchangir at redhat.com  Tue Feb 26 11:29:04 2019
From: mchangir at redhat.com (Milind Changire)
Date: Tue, 26 Feb 2019 16:59:04 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
Message-ID: <CAED=hWDN4AavnLiWagSiCHT-GmDKC3A=aGM=kgH-tYOsg1Q8OA@mail.gmail.com>

On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan <srangana at redhat.com>
wrote:

> Hi,
>
> There have been several crashes and issues reported by users on the
> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
> have a few more addressing the blockers against 5.4 [1].
>
> The original date was March 10th, but we would like to accelerate a 5.4
> release to earlier this month, once all critical blockers are fixed.
>
> Hence there are 3 asks in this mail,
>
> 1) Packaging team, would it be possible to accommodate an 5.4 release
> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
> we get the required fixes by then.
>
> 2) Maintainers, what other issues need to be tracked as blockers? Please
> add them to [1].
>
> 3) Current blocker status reads as follows:
> - Bug 1651246 - Failed to dispatch handler
>   - This shows 2 patches that are merged, but there is no patch that
> claims this is "Fixed" hence bug is still in POST state. What other
> fixes are we expecting on this?
>   - @Milind request you to update the status
>
Bug 1651246 has been addressed.
Patch has been merged on master
<https://review.gluster.org/c/glusterfs/+/22221> as well as release-5
<https://review.gluster.org/c/glusterfs/+/22237> branches.
Above patch addresses logging issue only.


> - Bug 1671556 - glusterfs FUSE client crashing every few days with
> 'Failed to dispatch handler'
>   - Awaiting fixes for identified issues
>   - @Nithya what would be the target date?
>
> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
> process
>   - Awaiting a fix, what is the potential target date for the same?
>   - We also need the bug assigned to a person
>
Bug 1671603 has been addressed.
Patch has been posted on master
<https://review.gluster.org/c/glusterfs/+/22126> and merged on release-5
<https://review.gluster.org/c/glusterfs/+/22127> branches.
Above patch addresses logging issue only.


> Thanks,
> Shyam
>
> [1] Release 5.4 tracker:
> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>


-- 
Milind
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190226/38c27cb6/attachment.html>

From amukherj at redhat.com  Tue Feb 26 11:50:40 2019
From: amukherj at redhat.com (Atin Mukherjee)
Date: Tue, 26 Feb 2019 17:20:40 +0530
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <CAED=hWDN4AavnLiWagSiCHT-GmDKC3A=aGM=kgH-tYOsg1Q8OA@mail.gmail.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAED=hWDN4AavnLiWagSiCHT-GmDKC3A=aGM=kgH-tYOsg1Q8OA@mail.gmail.com>
Message-ID: <CAGNCGH19gc7bEBu3QCSM3cyLYcaFJzPqNKsaupNxDCSSqUe6Xw@mail.gmail.com>

Milind - response inline.

Shyam - I'm not sure if you're tracking this. But at this point any blocker
bugs attached to 5.4 should also have clones of release-6 and attached to
the release tracker, otherwise we'll regress!

On Tue, Feb 26, 2019 at 5:00 PM Milind Changire <mchangir at redhat.com> wrote:

> On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan <srangana at redhat.com>
> wrote:
>
>> Hi,
>>
>> There have been several crashes and issues reported by users on the
>> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
>> have a few more addressing the blockers against 5.4 [1].
>>
>> The original date was March 10th, but we would like to accelerate a 5.4
>> release to earlier this month, once all critical blockers are fixed.
>>
>> Hence there are 3 asks in this mail,
>>
>> 1) Packaging team, would it be possible to accommodate an 5.4 release
>> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
>> we get the required fixes by then.
>>
>> 2) Maintainers, what other issues need to be tracked as blockers? Please
>> add them to [1].
>>
>> 3) Current blocker status reads as follows:
>> - Bug 1651246 - Failed to dispatch handler
>>   - This shows 2 patches that are merged, but there is no patch that
>> claims this is "Fixed" hence bug is still in POST state. What other
>> fixes are we expecting on this?
>>   - @Milind request you to update the status
>>
> Bug 1651246 has been addressed.
> Patch has been merged on master
> <https://review.gluster.org/c/glusterfs/+/22221> as well as release-5
> <https://review.gluster.org/c/glusterfs/+/22237> branches.
> Above patch addresses logging issue only.
>

Isn't this something which is applicable to release-6 branch as well? I
don't find https://review.gluster.org/#/c/glusterfs/+/22221/ in release-6
branch which means we're going to regress this in release 6 if this isn't
backported and marked as blocker to release 6.


>
>> - Bug 1671556 - glusterfs FUSE client crashing every few days with
>> 'Failed to dispatch handler'
>>   - Awaiting fixes for identified issues
>>   - @Nithya what would be the target date?
>>
>> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
>> process
>>   - Awaiting a fix, what is the potential target date for the same?
>>   - We also need the bug assigned to a person
>>
> Bug 1671603 has been addressed.
> Patch has been posted on master
> <https://review.gluster.org/c/glusterfs/+/22126> and merged on release-5
> <https://review.gluster.org/c/glusterfs/+/22127> branches.
>

Are you sure the links are correct? Patch posted against release 5 branch
is abandoned? And also just like above, same question for release-6 branch,
I don't see a patch?

Above patch addresses logging issue only.
>
>
>> Thanks,
>> Shyam
>>
>> [1] Release 5.4 tracker:
>> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>> _______________________________________________
>> maintainers mailing list
>> maintainers at gluster.org
>> https://lists.gluster.org/mailman/listinfo/maintainers
>>
>
>
> --
> Milind
>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190226/6152a31f/attachment.html>

From srangana at redhat.com  Tue Feb 26 13:57:04 2019
From: srangana at redhat.com (Shyam Ranganathan)
Date: Tue, 26 Feb 2019 08:57:04 -0500
Subject: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier
	than Mar-10th
In-Reply-To: <CAGNCGH19gc7bEBu3QCSM3cyLYcaFJzPqNKsaupNxDCSSqUe6Xw@mail.gmail.com>
References: <5c523b6f-1d3e-3771-d29d-b48929843379@redhat.com>
	<CAED=hWDN4AavnLiWagSiCHT-GmDKC3A=aGM=kgH-tYOsg1Q8OA@mail.gmail.com>
	<CAGNCGH19gc7bEBu3QCSM3cyLYcaFJzPqNKsaupNxDCSSqUe6Xw@mail.gmail.com>
Message-ID: <169ef0a7-fbf0-8667-485b-18cd679e050f@redhat.com>

Thank you all, merging the patches and tagging the release today.

Shyam
On 2/26/19 6:50 AM, Atin Mukherjee wrote:
> Milind - response inline.
> 
> Shyam - I'm not sure if you're tracking this. But at this point any
> blocker bugs attached to 5.4 should also have clones of release-6 and
> attached to the release tracker, otherwise we'll regress!
> 
> On Tue, Feb 26, 2019 at 5:00 PM Milind Changire <mchangir at redhat.com
> <mailto:mchangir at redhat.com>> wrote:
> 
>     On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan
>     <srangana at redhat.com <mailto:srangana at redhat.com>> wrote:
> 
>         Hi,
> 
>         There have been several crashes and issues reported by users on the
>         latest 5.3 release. Around 10 patches have been merged since 5.3
>         and we
>         have a few more addressing the blockers against 5.4 [1].
> 
>         The original date was March 10th, but we would like to
>         accelerate a 5.4
>         release to earlier this month, once all critical blockers are fixed.
> 
>         Hence there are 3 asks in this mail,
> 
>         1) Packaging team, would it be possible to accommodate an 5.4
>         release
>         around mid-next week (RC0 for rel-6 is also on the same week)?
>         Assuming
>         we get the required fixes by then.
> 
>         2) Maintainers, what other issues need to be tracked as
>         blockers? Please
>         add them to [1].
> 
>         3) Current blocker status reads as follows:
>         - Bug 1651246 - Failed to dispatch handler
>         ? - This shows 2 patches that are merged, but there is no patch that
>         claims this is "Fixed" hence bug is still in POST state. What other
>         fixes are we expecting on this?
>         ? - @Milind request you to update the status
> 
>     Bug 1651246 has been addressed.
>     Patch has been merged on master
>     <https://review.gluster.org/c/glusterfs/+/22221> as well as
>     release-5 <https://review.gluster.org/c/glusterfs/+/22237> branches.
>     Above patch addresses logging issue only.
> 
> 
> Isn't this something which is applicable to release-6 branch as well? I
> don't find https://review.gluster.org/#/c/glusterfs/+/22221/ in
> release-6 branch which means we're going to regress this in release 6 if
> this isn't backported and marked as blocker to release 6.
> 
> 
> 
>         - Bug 1671556 - glusterfs FUSE client crashing every few days with
>         'Failed to dispatch handler'
>         ? - Awaiting fixes for identified issues
>         ? - @Nithya what would be the target date?
> 
>         - Bug 1671603 - flooding of "dict is NULL" logging & crash of
>         client process
>         ? - Awaiting a fix, what is the potential target date for the same?
>         ? - We also need the bug assigned to a person
> 
>     Bug 1671603 has been addressed.
>     Patch has been posted on master
>     <https://review.gluster.org/c/glusterfs/+/22126> and merged on
>     release-5 <https://review.gluster.org/c/glusterfs/+/22127> branches.
> 
> 
> Are you sure the links are correct? Patch posted against release 5
> branch is abandoned? And also just like above, same question for
> release-6 branch, I don't see a patch?
> 
>     Above patch addresses logging issue only.
> 
> 
>         Thanks,
>         Shyam
> 
>         [1] Release 5.4 tracker:
>         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>         _______________________________________________
>         maintainers mailing list
>         maintainers at gluster.org <mailto:maintainers at gluster.org>
>         https://lists.gluster.org/mailman/listinfo/maintainers
> 
> 
> 
>     -- 
>     Milind
> 
>     _______________________________________________
>     maintainers mailing list
>     maintainers at gluster.org <mailto:maintainers at gluster.org>
>     https://lists.gluster.org/mailman/listinfo/maintainers
> 

From jenkins at build.gluster.org  Tue Feb 26 14:47:30 2019
From: jenkins at build.gluster.org (jenkins at build.gluster.org)
Date: Tue, 26 Feb 2019 14:47:30 +0000 (UTC)
Subject: [gluster-packaging] glusterfs-5.4 released
Message-ID: <1028668680.17.1551192450784.JavaMail.jenkins@jenkins-el7.rht.gluster.org>

SRC: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
HASH: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum

This release is made off jenkins-release-80

From ndevos at redhat.com  Wed Feb 27 10:19:53 2019
From: ndevos at redhat.com (Niels de Vos)
Date: Wed, 27 Feb 2019 11:19:53 +0100
Subject: [gluster-packaging] glusterfs-5.4 released
In-Reply-To: <1028668680.17.1551192450784.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
References: <1028668680.17.1551192450784.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
Message-ID: <20190227101953.GH3839@ndevos-x270>

On Tue, Feb 26, 2019 at 02:47:30PM +0000, jenkins at build.gluster.org wrote:
> SRC: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> HASH: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum

Packages for the CentOS Storage SIG are now available for testing.
Please try them out and report test results on this list.

  # yum install centos-release-gluster
  # yum install --enablerepo=centos-gluster5-test glusterfs-server

Thanks,
Niels

From ndevos at redhat.com  Thu Feb 28 13:01:03 2019
From: ndevos at redhat.com (Niels de Vos)
Date: Thu, 28 Feb 2019 14:01:03 +0100
Subject: [gluster-packaging] [Gluster-Maintainers] glusterfs-6.0rc0
	released
In-Reply-To: <20190222135153.GE2496@ndevos-x270>
References: <430948742.3.1550808940070.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
	<20190222135153.GE2496@ndevos-x270>
Message-ID: <20190228130103.GO3839@ndevos-x270>

On Fri, Feb 22, 2019 at 02:51:53PM +0100, Niels de Vos wrote:
> On Fri, Feb 22, 2019 at 04:15:39AM +0000, jenkins at build.gluster.org wrote:
> > SRC: https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.tar.gz
> > HASH: https://build.gluster.org/job/release-new/79/artifact/glusterfs-6.0rc0.sha512sum
> 
> When will the tarball land under
> https://download.gluster.org/pub/gluster/glusterfs/6 ?
> 
> I'll try to get the builds done today or over the weekend. The CentOS
> team will need to setup the sync from the buildsystem to the standard
> repository locations once the builds are available. Once its done, I'll
> let everyone know.

Packages from the CentOS Storage SIG are now available in the public
testing repository. Please use these packages to enable the repo and
install the glusterfs components in a 2nd step.

el7: https://cbs.centos.org/kojifiles/work/tasks/3263/723263/centos-release-gluster6-0.9-1.el7.centos.noarch.rpm
el6: https://cbs.centos.org/kojifiles/work/tasks/3265/723265/centos-release-gluster6-0.9-1.el6.centos.noarch.rpm

Once installed, the testing repo is enabled. Everything should be
available.

It is highly appreciated to let me know some results of the testing!

Thanks,
Niels

From kkeithle at redhat.com  Thu Feb 28 13:27:57 2019
From: kkeithle at redhat.com (Kaleb Keithley)
Date: Thu, 28 Feb 2019 08:27:57 -0500
Subject: [gluster-packaging] glusterfs-5.4 released
In-Reply-To: <1028668680.17.1551192450784.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
References: <1028668680.17.1551192450784.JavaMail.jenkins@jenkins-el7.rht.gluster.org>
Message-ID: <CAC+Jd5ArWY7WjqYJ39VoBDnr9jsaDRraJ_TEoyuRGiRicY06dg@mail.gmail.com>

glusterfs-5.4 packages for:

* Fedora 29 are in the Fedora Updates-Testing repo. Use `dnf` to install.
Fedora packages will move to the Fedora Updates repo after a nominal
testing period. Fedora 28 and Fedora 30 packages are at [1].

* RHEL 8 Beta are at [1].

* Debian Stretch/9 are on download.gluster.org at [1] (arm64 packages
coming soon.) Debian Buster/Sid/10 packages will land after an issue with
the Buster mirrors is resolved.

* Xenial/16.04, Bionic/18.04, Cosmic/18.10, and Disco/19.04 are on
Launchpad at [2].

* SUSE SLES12SP4, Tumbleweed, SLES15, and Leap15 will be on OpenSUSE Build
Service at [3] soon.

I have updated all the .../LATEST symlinks.

[1] https://download.gluster.org/pub/gluster/glusterfs/5
[2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-5
[3] https://build.opensuse.org/project/subprojects/home:glusterfs



On Tue, Feb 26, 2019 at 9:47 AM <jenkins at build.gluster.org> wrote:

> SRC:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> HASH:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>
> This release is made off
> jenkins-release-80_______________________________________________
> packaging mailing list
> packaging at gluster.org
> https://lists.gluster.org/mailman/listinfo/packaging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/packaging/attachments/20190228/e384cd29/attachment.html>