Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I don't think that redhat-upgrade-tool should automatically import the gpg keys. It doesn't *really* know what the keys are, since there isn't any data in the treeinfo files to indicate what they are, and this is an ongoing problem that goes all the way to bug 998. I did, however, fix the generated repo files so that the gpgcheck and gpgkey settings used in the post-upgrade scripts are the same as those used during the upgrade process, so errors like this shouldn't occur during post-upgrade.
Also, as a workaround for bug 1123915, redhat-upgrade-tool will automatically add /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release as the key for the main repo when the treeinfo contains "Red Hat Enterprise Linux". This also means that when upgrading, if the GPG key is not imported into RPM, the upgrade will fail during package download and indicate that the key needs to be imported.