Description of problem: We followed https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/sect-Disconnected_Satellite.html when setting up our environment for a disconnected Satellite. Upon rebooting the content host after hitting issues and troubleshooting, we couldn't get anything to talk with pulp until manually starting httpd, which wasn't running. I'm not sure if the issue is with step 11 in the docs, or a package/default config issue in katello-disconnected and related packages. Version-Release number of selected component (if applicable): katello-utils-1.5.16-1.el6sat ruby193-rubygem-katello-1.5.0-93.el6sat pulp-katello-0.3-4.el6sat How reproducible: every reboot Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
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.