Le mercredi 06 mars 2019 à 21:31 +0530, Sankarshan Mukhopadhyay a
écrit :
> On Wed, Mar 6, 2019 at 8:47 PM Michael Scherer
> wrote:
> >
> > Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
> > écrit :
> > > On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> > > wrote:
> > >
On Wed, Mar 6, 2019 at 8:47 PM Michael Scherer wrote:
>
> Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
> écrit :
> > On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> > wrote:
> > >
> > > Hello,
> > >
> > > Today while debugging the centos7-regression failed builds I saw
Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
écrit :
> On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> 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
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.mukhopadh...@gmail.com> wrote:
> On Wed, Mar 6, 2019 at 5:38 PM
On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
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] whi
