Re: [Gluster-devel] GlusterD2 - 4.0.0rc1 (warning: we have a blocker for GD2)

On Thu, Mar 1, 2018 at 12:52 PM, Kaushal M wrote: > On Wed, Feb 28, 2018 at 9:50 PM, Kaleb S. KEITHLEY > wrote: >> On 02/28/2018 10:49 AM, Kaushal M wrote: >>> We have a GlusterD2-4.0.0rc1 release. >>> >>> Aravinda, Prashanth and the rest of the GD2

Re: [Gluster-devel] GlusterD2 - 4.0.0rc1 (warning: we have a blocker for GD2)

On Thu, Mar 1, 2018 at 6:14 PM, Kaushal M wrote: > On Thu, Mar 1, 2018 at 12:52 PM, Kaushal M wrote: >> On Wed, Feb 28, 2018 at 9:50 PM, Kaleb S. KEITHLEY >> wrote: >>> On 02/28/2018 10:49 AM, Kaushal M wrote: We have a

[Gluster-devel] Smoke failing consistently on devrpm-fedora?

While going though patches, I see that from around Feb 28th, smoke is failing always, see [1]. The failure seems to have started as mock.py moved from 1.4.8 to 1.4.9. @Nigel/Kaleb, is this something that the changed in the infra, that has caused this, or just that with the latest mock we have

Re: [Gluster-devel] Release 4.0: Unable to complete rolling upgrade tests

On 03/02/2018 07:26 AM, Shyam Ranganathan wrote: Hi Pranith/Ravi, So, to keep a long story short, post upgrading 1 node in a 3 node 3.13 cluster, self-heal is not able to catch the heal backlog and this is a very simple synthetic test anyway, but the end result is that upgrade testing is

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: RC1 tagged

On 02/28/2018 07:25 AM, Javier Romero wrote: > This one fails > http://cbs.centos.org/kojifiles/work/tasks/1548/311548/centos-release-gluster40-0.9-1.el7.centos.x86_64.rpm > > # yum install -y >

[Gluster-devel] Release 4.0: Unable to complete rolling upgrade tests

Hi Pranith/Ravi, So, to keep a long story short, post upgrading 1 node in a 3 node 3.13 cluster, self-heal is not able to catch the heal backlog and this is a very simple synthetic test anyway, but the end result is that upgrade testing is failing. Here are the details, - Using

Re: [Gluster-devel] Release 4.0: Unable to complete rolling upgrade tests

On 03/02/2018 10:11 AM, Ravishankar N wrote: + Anoop. It looks like clients on the old (3.12) nodes are not able to talk to the upgraded (4.0) node. I see messages like these on the old clients:  [2018-03-02 03:49:13.483458] W [MSGID: 114007] [client-handshake.c:1197:client_setvolume_cbk]

Re: [Gluster-devel] Release 4.0: Unable to complete rolling upgrade tests

+ Anoop. It looks like clients on the old (3.12) nodes are not able to talk to the upgraded (4.0) node. I see messages like these on the old clients:  [2018-03-02 03:49:13.483458] W [MSGID: 114007] [client-handshake.c:1197:client_setvolume_cbk] 0-testvol-client-2: failed to find key

Re: [Gluster-devel] Release 4.0: Unable to complete rolling upgrade tests

On 03/02/2018 11:04 AM, Anoop C S wrote: On Fri, 2018-03-02 at 10:11 +0530, Ravishankar N wrote: + Anoop. It looks like clients on the old (3.12) nodes are not able to talk to the upgraded (4.0) node. I see messages like these on the old clients: [2018-03-02 03:49:13.483458] W [MSGID: