https://bugzilla.redhat.com/show_bug.cgi?id=1696518
Bug ID: 1696518
Summary: builder203 does not have a valid hostname set
Product: GlusterFS
Version: mainline
Status: NEW
Component: project-infrastructure
Assignee:
Le jeudi 04 avril 2019 à 19:10 +0300, Yaniv Kaul a écrit :
> I'm not convinced this is solved. Just had what I believe is a
> similar
> failure:
>
> *00:12:02.532* A dependency job for rpc-statd.service failed. See
> 'journalctl -xe' for details.*00:12:02.532* mount.nfs: rpc.statd is
> not
I'm not convinced this is solved. Just had what I believe is a similar
failure:
*00:12:02.532* A dependency job for rpc-statd.service failed. See
'journalctl -xe' for details.*00:12:02.532* mount.nfs: rpc.statd is
not running but is required for remote locking.*00:12:02.532*
mount.nfs: Either use
Thanks misc. I have always seen a pattern that on a reattempt (recheck
centos) the same builder is picked up many time even though it's promised
to pick up the builders in a round robin manner.
On Thu, Apr 4, 2019 at 7:24 PM Michael Scherer wrote:
> Le jeudi 04 avril 2019 à 15:19 +0200, Michael
Le jeudi 04 avril 2019 à 15:19 +0200, Michael Scherer a écrit :
> Le jeudi 04 avril 2019 à 13:53 +0200, Michael Scherer a écrit :
> > Le jeudi 04 avril 2019 à 16:13 +0530, Atin Mukherjee a écrit :
> > > Based on what I have seen that any multi node test case will fail
> > > and
> > > the
> > >
Le jeudi 04 avril 2019 à 13:53 +0200, Michael Scherer a écrit :
> Le jeudi 04 avril 2019 à 16:13 +0530, Atin Mukherjee a écrit :
> > Based on what I have seen that any multi node test case will fail
> > and
> > the
> > above one is picked first from that group and If I am correct none
> > of
> >
Le jeudi 04 avril 2019 à 16:13 +0530, Atin Mukherjee a écrit :
> Based on what I have seen that any multi node test case will fail and
> the
> above one is picked first from that group and If I am correct none of
> the
> code fixes will go through the regression until this is fixed. I
> suspect it
Based on what I have seen that any multi node test case will fail and the
above one is picked first from that group and If I am correct none of the
code fixes will go through the regression until this is fixed. I suspect it
to be an infra issue again. If we look at
