Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Installing_a_RednbspHat_Satellite_Capsule_Server.html Section Number and Name: 5.3 Describe the issue: In Procedure 5.1, the 'subscription-manager list --available --all' command informs the user to select the Red Hat Satellite SKU, with the output of " +-------------------------------------------+ Available Subscriptions +-------------------------------------------+ ProductName: Red Hat Satellite ProductId: SKU123456 PoolId: e1730d1f4eaa448397bfd30c8c7f3d334bd8b Quantity: 10 Multi-Entitlement: No Expires: 08/20/2013 MachineType: physical " Satellite SKUs should not be used for deploying Capsules. Capsule SKUs for Capsules. Satellite SKUs for Satellites. Suggestions for improvement: * Change the output of 'subscription-manager list --available --all' to: Subscription Name: Red Hat Satellite Capsule Server Provides: Red Hat Satellite Proxy Red Hat Satellite Capsule Beta Red Hat Beta Red Hat Software Collections (for RHEL Server) Red Hat Satellite Capsule Red Hat Enterprise Linux Server Red Hat Enterprise Linux High Availability (for RHEL Server) Red Hat Software Collections Beta (for RHEL Server) Red Hat Enterprise Linux Load Balancer (for RHEL Server) SKU: MCT0369 Pool ID: 9e4cc4e9b9fb407583035861bb6be501 Available: 3 Suggested: 1 Service Level: Premium Service Type: L1-L3 Multi-Entitlement: No Ends: 10/07/2015 System Type: Physical This reflects an actual production SKU that an end-user would have. * Step 2 of procedure 5.1 can then be simplified to: "# subscription-manager subscribe --pool=Red_Hat_Satellite_Capsule_Pool_Id" This is due to the Capsule subscription providing access to RHEL, Red Hat Software Collections, and the bits for Red Hat Satellite Capsule Server. So, a single pool, which provides multiple repositories.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
*** Bug 1213789 has been marked as a duplicate of this bug. ***