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.

For Satellite versions 6.13 and older, and upstream Katello versions 4.8 and older, custom products will still be enabled by default. In these older versions, turning on SCA would mean that your hosts will suddenly get access to all custom products, even those that you hadn't attached a subscription for. This is unwanted behavior.

With this change, turning on SCA will also run a Dynflow task that adds "disabled" content overrides to your hosts and activation keys, for any content for which you don't have a subscription.

The effect of this is that once SCA is turned on, your hosts will have access to the same repositories as before, and won't suddenly get access to all custom products.

For newer Satellite and Katello versions, this change does not apply, because custom products are disabled by default.

Created from redmine issue https://projects.theforeman.org/issues/36301

Upstream bug assigned to jlenz

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36301 has been resolved.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.13.2 Async Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:4043