[Gluster-infra] Jenkins directory ownership and ansible

[Niels de Vos]

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#L18

Or, even after each smoke run?
  https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/smoke.sh#L21

> and:
> --- before
> +++ after
> @@ -1,5 +1,5 @@
>  {
> -    "group": 0,
> -    "owner": 0,
> +    "group": 502,
> +    "owner": 502,
>      "path": "/d/backends"
>  }
> changed: [slave28.cloud.gluster.org] => (item=/d/backends)
> 
> what is supposed to be the right perm for that directory, since it keep
> being changed by something ?
> 
> the corresponding ansible line:
> https://github.com/gluster/gluster.org_ansible_configuration/blob/master/roles/jenkins_builder/tasks/main.yml#L48
> 
> if /d/backends/ is not supposed to be readable/writable by jenkins
> (and/or owned), I can change it.

Not sure about the /d/backends dir. That may be done by the regression
tests in the glusterfs sources, but I did not spot it there.

Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/gluster-infra/attachments/20170215/6d918bea/attachment.sig>