Bug 1324218

Summary:	I would like a default location under /var/lib/pulp for repo exports
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Installer	Assignee:	Chris Duryee <cduryee>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, cwelton, jcallaha, mmccune, rjerrido, swadeley
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14698
Whiteboard:
Fixed In Version:	rubygem-katello-3.0.0.31-1,rubygem-katello-3.0.0.31-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:07:25 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:
Bug Depends On:
Bug Blocks:	1285244

Description Chris Duryee 2016-04-05 20:55:12 UTC

Description of problem:

Currently there is no default setting for repository exports. Given that users are aware that /var/lib/pulp/* can take a large amount of disk space, it makes sense for there to be a default dir (say, /var/lib/pulp/katello-exports) that houses repo exports. This would let repo export work "out of the box" without the user having to jump through permissions or SELinux hoops.

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

Comment 3 Bryan Kearney 2016-04-19 16:02:34 UTC

Upstream bug component is Installer

Comment 4 Bryan Kearney 2016-05-12 18:15:25 UTC

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

Comment 5 jcallaha 2016-05-23 17:48:03 UTC

Verified in Satellite 6.2 Beta Snap 12. 
There is currently a default location provided. That location is /var/lib/pulp/katello-export.

Comment 6 Bryan Kearney 2016-07-27 11:07:25 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