Customers will follow the instructions for setting a synchronization host for synchronizing content for a Disconnected Satellite. https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/sect-Disconnected_Satellite.html Unfortunately, pulp (the backing server hosting the content) does not export ISO/images to a directory structure friendly for use by RHCI as a CDN. The ISO/images are put in a top directory cf-me-5_4-for-rhel-6-files--x86_64/ instead of being in the content/ directory. Pulp is adding support for this, but in the mean time we need to document that after exporting and expanding the content: # katello-disconnected export -t /var/tmp/export # ./expand_export.sh *** Done expanding archives. *** The user needs to post process the results with the following commands: # fix cf-me image files mkdir -p $EXPORT_DIR/content/dist/cf-me/server/5.5/x86_64/files/ mkdir -p $EXPORT_DIR/content/dist/cf-me/server/5.4/x86_64/files/ mv cf-me-5_5-for-rhel-7-files--x86_64/* $EXPORT_DIR/content/dist/cf-me/server/5.5/x86_64/files/ mv cf-me-5_4-for-rhel-6-files--x86_64/* $EXPORT_DIR/content/dist/cf-me/server/5.4/x86_64/files/ # fix openstack directory files mkdir -p $EXPORT_DIR/content/dist/rhel/server/7/7Server/x86_64/openstack-director/7.0/files/ mv rhel-7-server-openstack-7_0-files-7Server-x86_64/* $EXPORT_DIR/content/dist/rhel/server/7/7Server/x86_64/openstack-director/7.0/files/ # recursively fix openstack listing files fix_listing_files $EXPORT_DIR/content/dist/rhel/server/7/7Server/x86_64/openstack-director/7.0/ true
Created attachment 1116349 [details] script to fix export This script will contain the commands the user should run or they can download the script and fix their exports more easily. Usage: ./fix_export.sh /path/to/export For example if your content lives in /var/tmp/export/content then pass in /var/tmp/export to the script.
*** Bug 1300045 has been marked as a duplicate of this bug. ***
Hi Jesus, Thank you for raising this bug. Given the current direction of QCI, only critical bugs are to be addressed in the documentation going forward. As such, I will be closing this bug, but please let me know if you have any questions or concerns. Kind regards, Andrew