Repositories are showing 0 packages after importing Content Views to a Disconnected Satellite 6.10.

Environment

• Red Hat Satellite 6.10.
• Disconnected Satellite 6.10.

Issue

• Exporting a content view version and importing it on a disconnected Satellite creates an unusable Content View version.

Resolution

• To force the publication of the imported repositories, follow the steps below:

  1. Identify the content-view version id of the repository:

  # hammer content-view version list 
  

  2. Use the content-view version id on the next command:

  # hammer content-view version republish-repositories --id=<version id> --force=true
  

• Now these repositories will be available to be used in a Content View and further imported.

• The issue is being tracked by Red Hat under Public Red Hat Bugzillas This content is not included.2030101, This content is not included.2043726, and This content is not included.2032602. For More Information, please open a This content is not included.support case with Red Hat Technical Support Team.

For more KB articles/solutions related to Red Hat Satellite 6.x Content View Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Content View Issues

Root Cause

• When importing the content views on the disconnected Satellite, they are intended to be "import-only". All content views defined as import-only don't have a publication, meaning they are not to be used as regular content views. They are used only for importing content.
• That being said, force a publication of such repositories and then they will be available or can create repositories with the content made available on the disconnected satellite by the import process.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.