Le mercredi 15 février 2017 à 13:58 +0100, Niels de Vos a écrit :
> On Wed, Feb 15, 2017 at 01:02:32PM +0100, Michael Scherer wrote:
> > Hi
> >
> > (yes, again me)
> >
> > so I started to look at ansible automated run logs, and I stumbled on a
> > few puzzling ones:
> >
> > --- before
> > +++ after
> > @@ -1,6 +1,6 @@
> > {
> > - "group": 0,
> > - "owner": 0,
> > + "group": 502,
> > + "owner": 502,
> > "path": "/var/lib/glusterd",
> > - "state": "absent"
> > + "state": "directory"
> > }
> > changed: [slave0.cloud.gluster.org] => (item=/var/lib/glusterd)
> >
> > so why did /var/lib/glusterd disappeared on slave0.cloud.gluster.org and
> > slave34, for a start ?
>
> I think it is possible that the /var/lib/glusterd directory is removed
> in case it was empty:
>
> https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/cleanup.sh#L18Indeed, could be it > Or, even after each smoke run? > > https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/smoke.sh#L21 More likely. Changing that is not going to break any tests ? IE, how is gluster supposed to react if /var/lib/glusterd is not here, is that something we want to test ? -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-infra mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-infra
