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?
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.