How to verify subscriptions via the manifest on Satellite 6.

Solution In Progress - Updated -

Environment

  • Red Hat Satellite 6
  • Subscription Manager

Issue

  • What is the best way to verify the subscriptions that are available from a Manifest in Satellite 6?
    The repositories should be available depending on the subscriptions that are attached to the manifest, however if any error occurs the following is a good way to verify that the repositories are associated with the entitlement.

Resolution

  • The following steps can be performed to locate if the Satellite has the required entitlements for the channel that is being enabled.

The pem file can be found by either downloading the certificate or the manifest directly from the following location:
Customer Portal -> My Subscriptions -> Satellite -> Select the Satellite -> Download Manifest or Certificate

Once the file is download, you can then run then inside your command line using the rct command that is provided by the subscription-manager package.
If the file is accessed from the manifest, you will first have to unzip the manifest and then the consumer_export.zip to reveal the pem file

# unzip manifest*.zip
# unzip consumer*.zip
# ls -l export/entitlement_certificates/xxxxxxxxxxxxxxxxxxxx.pem

Then you can run the rct again the pem file. The output may be quite large depending on the amount of entitlements, if that is the case you can add multiple greps, to narrow down to the subscription that you cannot access.

# rct  cat-cert xxxxxxxxxxxxxxxx.pem | grep URL 
URL: /content/eus/rhel/server/6/$releasever/$basearch/optional/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/rh-common/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/rhn-tools/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/supplementary/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/oracle-java/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/highavailability/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/loadbalancer/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/resilientstorage/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/devtoolset/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/devtoolset/2/os
URL: /content/eus/rhel/server/6/$releasever/$basearch/rhscl/1/os

Root Cause

  • This issue can be caused if the manifest provides the channels, but there is a mismatch between the certificate and what the Red hat Account is providing.

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.

1 Comments

Once a manifest is activated in Satellite6, where does it keep it...what is the activate /path/to/manifest? ie.. in Satellite 5.8 it kept it in /etc/sysconfig/rhn/rhsm-manifest.zip which gives me the ability to back it up via cli...so that I can roll back when something breaks.