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.
Hello,
Many thanks for using the Direct Documentation Feedback tool to report this issue.
The documentation team will look into it and share updates about the fix in this ticket.
Thank you!
Comment 3Aneta Šteflová Petrová
2023-09-06 06:28:56 UTC
(In reply to Direct Docs Feedback from comment #0)
> This menu item no longer exists in version 6.12.4.
>
> Reported by: dcsunix
>
> https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/
> managing_content/managing_red_hat_subscriptions_content-
> management#annotations:806022e2-b24b-4324-866e-cac47fa19111
The procedure in 3.6. Attaching Red Hat Subscriptions to Content Hosts is only applicable if Simple Content Access (SCA) is disabled. This is highlighted at the beginning of the section (see the Important box). SCA is enabled by default for newly created organizations.
With SCA enabled, step 4 of the procedure is not available.
With SCA disabled, the step is available.
I suspect that the reporter had SCA enabled, and that's why they were unable to perform the procedure.
For more details on SCA, see https://access.redhat.com/articles/simple-content-access in Red Hat Knowledgebase.
Comment 4Aneta Šteflová Petrová
2023-09-06 06:32:15 UTC
I looked over the whole section 3.6. Attaching Red Hat Subscriptions to Content Hosts to see if I can rearrange the information or change it in any way to make it clearer that the steps depend on SCA being disabled, but I couldn't think of anything reasonable. Therefore, I'm closing this BZ per the explanation provided in comment#3.
If anyone disagrees or has any ideas about what to fix, don't hesitate to reopen.