RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Subscription Manager now sets gpgcheck = 0 if it sees that the gpgkey URL is not set. (Previously this would have been set to 1, meaning the repo would not function at all in this scenario, unless they were manually importing gpg keys on all their clients.) 

If someone uses custom content, not specifying a gpgkey URL when they set up their content, but manually importing the keys themselves on all clients, then gpgcheck is flipped to 0 after upgrading to the latest subscription manager, and they probably wouldn't even know. 

This needs release noted in the entitlements section, something like:

""" 
Subscription Manager will now disable gpgcheck for any repositories it manages which have an empty gpgkey. To re-enable, you can upload your GPG keys, and ensure that the correct URL is added to your custom content definition. 
"""

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Subscription Manager now disables gpgcheck for any repositories it manages which have an empty gpgkey. To re-enable the repository, upload the GPG keys, and ensure that the correct URL is added to your custom content definition.

Included in both 6.3 Release and Technical Notes.

Fix available on docs.redhat.com. Closing!