Il 07/02/20 14:51, Strahil Nikolov ha scritto:
> On February 7, 2020 10:30:19 AM GMT+02:00, Christian Reiss
> wrote:
>> Hey,
>>
>> the ACL issue did not occur during an upgrade. I did upgrade the broken
>>
>> cluster to get rid of the error. The version was oVirt node 4.3.7 with
>> the shipped
On February 7, 2020 10:30:19 AM GMT+02:00, Christian Reiss
wrote:
>Hey,
>
>the ACL issue did not occur during an upgrade. I did upgrade the broken
>
>cluster to get rid of the error. The version was oVirt node 4.3.7 with
>the shipped gluster version. I upgraded to 4.3.8 with Gluster 6.7 and
Hey,
the ACL issue did not occur during an upgrade. I did upgrade the broken
cluster to get rid of the error. The version was oVirt node 4.3.7 with
the shipped gluster version. I upgraded to 4.3.8 with Gluster 6.7 and
let's see how production ready this really is.
-Chris.
On 07/02/2020
Hi,
this is interesting, this happen always with gluster 6.6 or only in
certain cases?
I ask this because I have two ovirt clusters with gluster, both with
gluster v6.6, in one case I've upgraded from 6.5 to 6.6 as Strahil, and
I haven't hit this bug.
When upgrading my clusters I follow exactly
4 matches
Mail list logo
