Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-15422

[Docs] Update content view import pre-requisites to include checking manifest version in customer portal

XMLWordPrintable

    • 0
    • False
    • Moderate
    • None
    • None
    • None
    • Manual

      Document URL:
      (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Using_Upstream_Server_to_Sync_Content_View_Versions_content-management)

      Section Number and Name:
      9.1.2. Using an Upstream Satellite Server to Sync Content View Versions

      Describe the issue:

      • On the downstream Satellite Server, there is no mention of checking if:
        1. The manifest in the Red Hat Customer Portal is set to the correct Satellite version.
        2. The manifest contains the subscriptions required to entitle all repositories in the exported content view.

      Suggestions for improvement:

      • Before importing content views in the downstream Satellite Server:
        1. Confirm that the manifest (for downstream Satellite) is set to the correct Satellite version in the Red Hat Customer Portal
        2. The manifest contains subscriptions required to entitle all repositories in the content view to be imported.

      Additional information:

      • Customer reported failing content view imports despite meeting all pre-requisites.
      • Cause: manifest in the Red Hat Customer Portal was set to an older version than the downstream Satellite.

      [Blog] How to create and use a Red Hat Satellite manifest
      (https://www.redhat.com/en/blog/how-create-and-use-red-hat-satellite-manifest)

              jira-bugzilla-migration RH Bugzilla Integration
              rhn-support-swachira@redhat.com Sam Wachira
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: