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.

Docs RFE (probably Provisioning Guide could be a good candidate):

When RHEL8 kickstart BaseOS repository is synced, Pulp automatically includes all sub-repositories as unmanaged repositories. This effectively mean that AppStream sub-repository these cannot be managed, only published or promoted but it is not possible to filter packages, errata or any advanced operations.

In order to successfully provision a RHEL8 system, both BaseOS and AppStream repositories must be present. Therefore we need to recommend to always kickstart systems from repositories without any advanced content operations (I am not sure if "unmanaged" is a good term we should probably find something) and configure systems to subscribe to managed content after installation by providing valid and fully managed content view with RHEL BaseOS and AppStream as well as additional repositories.

Hope it makes sense, this is not my expertise so probably someone from Katello or Pulp could fill the details.

https://projects.theforeman.org/issues/33676

Content at https://docs.theforeman.org/nightly/Provisioning_Guide/index-foreman-el.html#using-a-synced-kickstart-repository_provisioning