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.

This section is relevant not only to RHEL 9, but all RHEL versions (6,7,8,9) and also architectures. Arch and OS version restrictions are already covered briefly in the procedure steps for creating custom products, but this section's title and content should be updated as well to reflect the true scope (all RHELs, and arch as well as OS version.) It should also be stated that arch and OS version restrictions are intended to be set only for custom products, as Red Hat repositories have these set automatically.

Reported by: rhn-engineering-jlenz

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/managing_content/importing_content_content-management#annotations:0a987568-ba2b-4252-bde6-b9c59a2f0082

Looking at the procedure in 5.24. Restricting Custom Repositories to RHEL 9 in Satellite and the steps that are performed in the web UI, the procedure itself will also need some tweaking.

Pull request submitted for review: https://github.com/theforeman/foreman-documentation/pull/2302

PR merged: https://github.com/theforeman/foreman-documentation/pull/2302#issuecomment-1665534249

The updated document is available: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/managing_content/importing_content_content-management#Restricting_a_Custom_Repository_to_a_Specific_OS_Version_or_Architecture_in_Project_content-management