Yes, Mohit is looking into it. There's some issue in the patch itself.
I forgot to link the bug filed for this: https://bugzilla.redhat.com/show_bug.cgi?id=1685813
On Wed, Mar 6, 2019 at 5:54 PM Sankarshan Mukhopadhyay <sankarshan.mukhopadhyay@xxxxxxxxx> wrote:
On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
<dkhandel@xxxxxxxxxx> wrote:
>
> Hello,
>
> Today while debugging the centos7-regression failed builds I saw most of the builders did not pass the instance status check on AWS and were unreachable.
>
> Misc investigated this and came to know about the patch[1] which seems to break the builder one after the other. They all ran the regression test for this specific change before going offline.
> We suspect that this change do result in infinite loop of processes as we did not see any trace of error in the system logs.
>
> We did reboot all those builders and they all seem to be running fine now.
>
The question though is - what to do about the patch, if the patch
itself is the root cause? Is this assigned to anyone to look into?
> Please let us know if you see any such issues again.
>
> [1] https://review.gluster.org/#/c/glusterfs/+/22290/
--
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
_______________________________________________
Gluster-infra mailing list
Gluster-infra@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-infra
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
