Bug 1012029 - katello-disconnected and possibly other utils should be packaged standalone
katello-disconnected and possibly other utils should be packaged standalone
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Inter Satellite Sync (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-09-25 11:06 EDT by Corey Welton
Modified: 2016-02-08 13:23 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-08 13:23:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Corey Welton 2013-09-25 11:06:35 EDT
Description of problem:

The katello-disconnected utility is expected to be run standalone on a
system, versus tied in on a box hosting satellite6.

That said, when installing katello-utils (the package which contains
katello-disconnected), we're basically pulling in almost all of the
standard katello packages anyway.

I'm wondering but if we shouldn't package this utility (and others?) in
a manner that does not require so much of the regular katello bits?
Comment 4 Bryan Kearney 2016-02-08 13:23:22 EST
The katello-disconnected server synchronization and export functions are being moved into the Satellite server itself. With 6.2, the katello-disconnected command will no longer be delivered and instead will be replaced with a new export and import functions delivered via the UI and hammer CLI. This bug is being closed as "WONTFIX" since it relates only to the existing katello-disconnected tooling. Please check the Satellite docs with the release of Satellite 6.2 on how to use the new content export and import features.

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