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.

Users should not be required to perform the additional manual step of associating Operating Systems with the Global Registration templates. This error during registration causes confusion with our users and introduces a manual step that in the majority of cases should just be handled automatically:

# curl -X GET "https://sat.example.com:9090/register?activation_key=..." -H 'Authorization: Bearer ' | bash
...
The system has been registered with ID: 93128d6d-d643-4915-8a78-01ce85b97ebe
The registered system name is: dhcp-8-30-40.lab.eng.rdu2.redhat.com
ERROR: not_found
Unable to find registration template for host client1.example.com running RedHat 7.9, associate the registration template for this OS first
#

Every Red Hat Enterprise Linux OS created via synchronizing kickstart repositories should automatically associate to the Global Registration template

Mike, I think this can be closed. 6.9 is based on 3.18.1 and the Redmine associated landed in 3.18.0

Can confirm, this has already landed in a snap

If this is already in a snap, could we get it out of post?

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 (Moderate: Satellite 6.9 Release), 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/RHSA-2021:1313