Bug 1623797

Summary: ERROR: Build root is locked by another process. (only on EL6 tests?
Product: [Community] GlusterFS Reporter: Yaniv Kaul <ykaul>
Component: project-infrastructureAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-infra, nigelb
Target Milestone: ---   
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: 2018-08-30 08:53:11 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 Yaniv Kaul 2018-08-30 08:31:33 UTC
Description of problem:
For example, from https://build.gluster.org/job/devrpm-el6/11531/console :

00:01:37.735 Wrote: /home/jenkins/root/workspace/devrpm-el6/extras/LinuxRPM/rpmbuild/SRPMS/glusterfs-4.2dev-0.412.git1aa23cb.el7.src.rpm
00:01:37.766 mv rpmbuild/SRPMS/* .
00:01:38.297 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)...
00:01:38.330 Start: init plugins
00:01:38.354 INFO: selinux enabled
00:01:38.368 Finish: init plugins
00:01:38.370 Start: run
00:01:38.381 INFO: Start(glusterfs-4.2dev-0.412.git1aa23cb.el7.src.rpm)  Config(epel-6-x86_64)
00:01:38.381 Start: clean chroot
00:01:38.388 ERROR: Exception(glusterfs-4.2dev-0.412.git1aa23cb.el7.src.rpm) Config(epel-6-x86_64) 0 minutes 0 seconds
00:01:38.388 INFO: Results and/or logs in: /home/jenkins/root/workspace/devrpm-el6/RPMS/el6/x86_64/
00:01:38.388 INFO: Cleaning up build root ('cleanup_on_failure=True')
00:01:38.388 Start: clean chroot
00:01:38.399 ERROR: Build root is locked by another process.
00:01:38.430 Build step 'Execute shell' marked build as failure
00:01:38.460 Archiving artifacts
00:01:42.384 Finished: FAILURE

Comment 1 Nigel Babu 2018-08-30 08:53:11 UTC

*** This bug has been marked as a duplicate of bug 1623452 ***