Bug 1324218 - I would like a default location under /var/lib/pulp for repo exports
Summary: I would like a default location under /var/lib/pulp for repo exports
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Chris Duryee
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1285244
TreeView+ depends on / blocked
 
Reported: 2016-04-05 20:55 UTC by Chris Duryee
Modified: 2019-09-25 21:18 UTC (History)
6 users (show)

Fixed In Version: rubygem-katello-3.0.0.31-1,rubygem-katello-3.0.0.31-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:07:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14698 0 None None None 2016-04-22 15:48:23 UTC

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
Note You need to log in before you can comment on or make changes to this bug.