Bug 1488125

Summary: builder0.int.rht.gluster.org and builder1 fail to run rpmbuild tests in mock
Product: [Community] GlusterFS Reporter: Niels de Vos <ndevos>
Component: project-infrastructureAssignee: bugs <bugs>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-infra, mscherer, nigelb
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-27 04:53:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Niels de Vos 2017-09-04 11:54:34 UTC
Description of problem:
Building remotely on builder0.int.rht.gluster.org (rpm7) in workspace /home/jenkins/workspace/devrpm-fedora
Wiping out workspace first.
java.nio.file.AccessDeniedException: /home/jenkins/workspace/devrpm-fedora/RPMS/fc25/x86_64/root.log

And the smoke test is marked with a failure.

Examples:
- https://build.gluster.org/job/devrpm-fedora/5789/console
- https://build.gluster.org/job/devrpm-el6/5754/

Both builders have been disabled until this is resolved.

13:03 < ndevos> nigelb, misc: builder0.int.rht.gluster.org seems to have a weird failure - https://build.gluster.org/job/devrpm-fedora/5786/console
13:04 < ndevos> oh, and builder1 has that as well - https://build.gluster.org/job/devrpm-el6/5751/console
13:44 < misc> ndevos: looking
13:44 < misc> mhh
13:44 < misc> ndevos: can you log it as a bugzilla ticket, seems to be a bit more complicated than a quick fix :/

Comment 1 M. Scherer 2017-09-04 12:15:18 UTC
Ok so it seems that mock is using root:
$ ls -ld /home/jenkins/workspace/devrpm-fedora/RPMS/
drwxrwxr-x. 3 root root 4096  4 sept. 08:51 /home/jenkins/workspace/devrpm-fedora/RPMS/

I guess that's related to:

https://github.com/gluster/gluster.org_ansible_configuration/pull/13#discussion_r136525704

I am cherrypicking the fix

Comment 2 M. Scherer 2017-09-04 12:22:54 UTC
So looking at it, it seems that if jenkins can't write to the workspace directory found, it then go to its home. Then it create the workspace and then fail with mock.

I am reenabling the builder on ansible fixed it, please redisable and complete that bug report if it still fail.