Bug 1311738 - verify config setting before repo export
verify config setting before repo export
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: --
Assigned To: Chris Duryee
Katello QA List
: Triaged
Depends On: 1314299
  Show dependency treegraph
Reported: 2016-02-24 15:58 EST by Tom McKay
Modified: 2016-07-27 05:23 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-27 05:23:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 13885 None None None 2016-04-22 10:58 EDT
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 08:28:58 EDT

  None (edit)
Description Tom McKay 2016-02-24 15:58:11 EST
In the planning step, confirm that the export dir setting is set, exists, and is writable.
Comment 1 Tom McKay 2016-02-24 15:58:13 EST
Created from redmine issue http://projects.theforeman.org/issues/13885
Comment 2 Tom McKay 2016-02-24 15:58:16 EST
Upstream bug assigned to mmccune@redhat.com
Comment 5 Bryan Kearney 2016-03-03 14:05:37 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/13885 has been closed
Chris Duryee
Applied in changeset commit:katello|a905ae018dfea5186af7d371f82d73a64cd25275.
Comment 6 Jitendra Yejare 2016-03-10 04:10:04 EST
Verified in latest Satellite 6.2 Snap 3.

The export sets(But doesn't creates any new and doesnt changes the owner to foreman), verifies dir existance and its writable.

Comment 9 errata-xmlrpc 2016-07-27 05:23:25 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.