On Fri, Mar 9, 2018 at 10:38 AM, Raghavendra Gowdappa
wrote:
>
>
> On Fri, Mar 2, 2018 at 11:01 AM, Ravishankar N
> wrote:
>
>>
>> On 03/02/2018 10:11 AM, Ravishankar N wrote:
>>
>>> + Anoop.
>>>
>>> It looks like clients on the old (3.12) nodes are
On Fri, Mar 2, 2018 at 11:01 AM, Ravishankar N
wrote:
>
> 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:
>>
>>
Forwarding to the devel and users groups as well.
We have tagged 4.0.0 branch as GA, and are in the process of building
packages.
It would a good time to run final install/upgrade tests if you get a
chance on these packages (I am running off to do the same now).
Thanks,
Shyam
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-08-2a1adc5c
___
Gluster-devel mailing list
Gluster-devel@gluster.org
Hi,
There is a core for test case: ./tests/bugs/rpc/bug-847624.t.
*link*: https://build.gluster.org/job/centos7-regression/232/console
Requesting concerned team to look into this.
Susant
___
Gluster-devel mailing list
Gluster-devel@gluster.org