Bug 1558118

Summary:	Accessing tarball of core fails with FORBIDDEN
Product:	[Community] GlusterFS	Reporter:	Raghavendra G <rgowdapp>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer, nigelb, spalai
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-03-21 15:09:23 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 Raghavendra G 2018-03-19 16:37:24 UTC

Description of problem:

I am not able to download the archive of core from:
http://builder102.cloud.gluster.org/archived_builds/build-install-centos7-regression-387.tar.bz2

bash-4.4$ wget http://builder102.cloud.gluster.org/archived_builds/build-install-centos7-regression-387.tar.bz2
--2018-03-19 17:56:14--  http://builder102.cloud.gluster.org/archived_builds/build-install-centos7-regression-387.tar.bz2
Resolving builder102.cloud.gluster.org (builder102.cloud.gluster.org)... 192.237.253.99
Connecting to builder102.cloud.gluster.org (builder102.cloud.gluster.org)|192.237.253.99|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2018-03-19 17:56:15 ERROR 403: Forbidden.

Regression job:
https://build.gluster.org/job/centos7-regression/387/consoleFull

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nigel Babu 2018-03-21 07:25:36 UTC

*** Bug 1558827 has been marked as a duplicate of this bug. ***

Comment 2 Nigel Babu 2018-03-21 07:26:27 UTC

This is now fixed. We set selinux fcontext during setup, but I don't think we run restorecon during our regular ansible runs. leaving the bug open for misc to debug.

Comment 3 M. Scherer 2018-03-21 15:09:23 UTC

Mhh, I wonder if that wasn't the builder being down when I tried to fix the others. I never connected to this one so I guess that why it was missed.

Also, I found out that we seems to never remove socket in /run/gluster :/

I ran a restorecon on /, so the problem is fixeD.