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.

See blocks bz for reasoning why we wish to change the way we provide the GPG signing keys for RHEL6 and later by allowing the distribution of multiple signing keys in a single file.

In /etc/pki/rpm-gpg/
cat 
RPM-GPG-KEY-redhat-release-2 + RPM-GPG-KEY-redhat-auxiliary
> RPM-GPG-KEY-redhat-release

distribute RPM-GPG-KEY-redhat-release, remove RPM-GPG-KEY-redhat-release-2 and RPM-GPG-KEY-redhat-auxiliary

(If you prefer to keep the keys separate in the tarball and simply merge them in %install of spec, that's fine too)

  Note: "yum import" is happy to import multiple keys in a given
  file (note the keys need to be separately armoured just like we
  do with our CA files, i.e. as 'cat' above, not an exported GPG keyring).

  Note: It's possible legacy users might "rpm --import" a file with
  multiple keys.  Shipped versions of RPM will only import the first
  listed key.  RPM upstream since May 2010 handles multiple keys and
  this will be in RHEL6 before GA (bz#586827)

How about the following?

RPM-GPG-KEY-redhat-legacy-former
RPM-GPG-KEY-redhat-legacy-rhx
RPM-GPG-KEY-redhat-legacy-release

I don't see a reason not to ship those.

With redhat-release-server-5.90Server-6.0.0.31.el6 there's the RPM-GPG-KEY-redhat-release which contains 2 keys, and 
RPM-GPG-KEY-redhat-legacy-former
RPM-GPG-KEY-redhat-legacy-rhx
RPM-GPG-KEY-redhat-legacy-release   which contain only one key.

Mark,
is the intention to keep the legacy files as is or to merge them with the redhat-release file?

intention was to keep legacy files as-is; I suppose we could merge legacy-former and legacy-release but I don't see any real need to do so.

Moving to VERIFIED then.

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.