Common manifest upload, update and refresh issues observed in Red Hat Satellite 6.

Red Hat Satellite 6 imports content from the Red Hat Content Delivery Network (CDN). Satellite 6 requires a Subscription Manifest to find, access, and download content from the corresponding repositories.

One must have a Subscription Manifest containing a subscription allocation for each organization on Satellite Server.

All subscription information is available in your Red Hat Customer Portal account.

Documentation

Red Hat Satellite 6.6 - Managing Subscriptions

This is the official product documentation that explains how the manifest can be imported, updated and used.

Common issues observed while importing, updating and refreshing manifest

• Unable to add Future Dated Subscriptions in Red Hat Satellite Manifest.
• What are the different ways to refresh Red Hat Satellite Manifest and how to automate the manifest refresh?
• How to create and upload or update and refresh a manifest to the Red Hat Satellite 6 server?
• Getting error Owner has already imported from another subscription management application while uploading a manifest on Red Hat Satellite 6.
• Importing manifest fails with error Katello::Errors::CandlepinError: Owner has already imported from another subscription management application
• After successfully adding subscriptions into manifest the subscriptions are not showing up on the Red Hat Satellite GUI.
• How to add/update Subscription in an imported manifest using Red Hat Satellite Web UI ?
• How to upload manifest for Red Hat Satellite 6 with Hammer CLI?
• Getting error Subscription allocation information is not available while creating new manifest.
• Manifest Refresh fails with Invalid credentials or RestClient::BadRequest: 400 Bad Request error in Red Hat Satellite 6

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