Bug 1321589

Summary:	unable to export repository directly to /var/www/html/pub/export
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Content Management	Assignee:	Chris Duryee <cduryee>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, cwelton, jcallaha, swadeley
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14362
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:29:20 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:
Bug Depends On:	1314299
Bug Blocks:

Description Chris Duryee 2016-03-28 14:20:41 UTC

Description of problem:

It is a common use case for users to want to export a repo directly to the '/var/www/html/pub/export' directory. If you attempt this with Sat 6.2 snapshot 5, you'll get an selinux denial.

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


How reproducible: every time


Steps to Reproduce:
1. create dir with correct permission, and set pulp_export_destination to /var/www/html/pub/export
2. attempt to export a repository

Actual results: error, and selinux denial


Expected results: successful export


Additional info: Exporting directly to /var/www/html/pub/export was not intended as an original use case, but seems popular enough to warrant adding a rule for this.

Comment 3 Bryan Kearney 2016-03-28 22:07:45 UTC

Upstream bug component is Content Management

Comment 4 Bryan Kearney 2016-03-28 22:07:48 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/14362 has been closed

Comment 5 jcallaha 2016-04-06 14:11:38 UTC

Verified in Satellite 6.2 Beta Snap 6 Compose 2.

Comment 7 errata-xmlrpc 2016-07-27 09:29:20 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501