Hi,
This looks like a cleanup issue. The infrastructure was being used for
Redant tests yesterday. Will take care of the cleanup part before today’s
run.
On Thu, 30 Dec 2021 at 10:20 AM, Amar Tumballi wrote:
> Any PR to suspect here?
>
> On Thu, Dec 30, 2021 at 6:25 AM Gluster-jenkins <
>
On Thu, Dec 30, 2021 at 5:50 AM Amar Tumballi wrote:
> Any PR to suspect here?
>
The previous execution that passed was based on commit 12b44fe. This one is
based on commit b8e32c3. The only commit between them is b8e32c3, but it
seems unlikely that it may affect non SSL connections.
It seems
Any PR to suspect here?
On Thu, Dec 30, 2021 at 6:25 AM Gluster-jenkins
wrote:
> *Test details:*
> RPM Location: Upstream
> OS Version: Red-Hat-Enterprise-Linux 8.4-(Ootpa)
> Baseline Gluster version: glusterfs-10.0-1
> Current Gluster version: glusterfs-20211228.b8e32c3-0.0
> Intermediate
Test details:
RPM Location: Upstream
OS Version: Red-Hat-Enterprise-Linux 8.4-(Ootpa)
Baseline Gluster version: glusterfs-10.0-1
Current Gluster version: glusterfs-20211228.b8e32c3-0.0
Intermediate Gluster version: No intermediate baseline
Test type:
