Bug 1012029

Summary:	katello-disconnected and possibly other utils should be packaged standalone
Product:	Red Hat Satellite	Reporter:	Corey Welton <cwelton>
Component:	Inter Satellite Sync	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.2	CC:	bkearney
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-08 18:23:22 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:

Description Corey Welton 2013-09-25 15:06:35 UTC

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 18:23:22 UTC

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.