Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The 'Chapter 2. Creating an Activation Key for Virtual Machines' and 'Chapter 3. Attaching a Host-based Subscription to Hypervisors' within 'Configuring Virtual Machine Subscriptions in Red Hat Satellite' doc is no more valid as Satellite has SCA enabled
Document URL:
https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/configuring_virtual_machine_subscriptions_in_red_hat_satellite/index?lb_target=preview
Section Number and Name:
Chapter 2. Creating an Activation Key for Virtual Machines
Chapter 3. Attaching a Host-based Subscription to Hypervisors
Describe the issue:
Satellite 6.13 has by default SCA enabled on it. If SCA is enabled, then there is no option to add Subscriptions to the Activation Key and to attach subscriptions to the hosts/hypervisors on Content Hosts page. Hence the steps mentioned in above 2 Chapters are not valid since Satellite has SCA enabled.
Suggestions for improvement:
There should be a disclaimer or a note added for both of these chapters which should mention that these chapters/steps are valid only if SCA is disabled on Satellite and Satellite has by default SCA enabled on it.
Additional information: "Chapter 6. Registering Virtual Machines to use a Host-based Subscription" in same documentation is also only valid if SCA is disabled on Satellite. If SCA is enabled, user should always prefer registering client to Satellite using Global Registration feature mentioned in 'Chapter 3. Registering Hosts to Satellite' in 'Managing Hosts' documentation. And not using the subscription-manager command mentioned in "Chapter 6. Registering Virtual Machines to use a Host-based Subscription" as this is a deprecated method.