Description of problem: When an export is not successful (for a variety of reasons), it's possible that the CLI does not clearly indicate a failure Version-Release number of selected component (if applicable): Satellite-6.0.2-RHEL-6-20131202.0 How reproducible: Steps to Reproduce: 1. Attempt to export into a location where there is not enough storage. 2. View results 3. Actual results: Archiving contents of /var/tmp/export into 4600M tar archives. NOTE: This may take a while. split: /var/tmp/export/content-export-01: No space left on device Done exporting content, please copy /var/tmp/export/* to your disconnected host Expected results: Archiving contents of /var/tmp/export into 4600M tar archives. NOTE: This may take a while. split: /var/tmp/export/content-export-01: No space left on device ERROR: There was an issue exporting content. Reason: $reason ^ This should be done for any detected issue exporting, really. Additional info:
Another example of when an error should be thrown is if user hits ^C to cancel. ERROR: There was an issue exporting content. Reason: User cancelled export.
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.