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.

Description of problem:
When importing the Elastic repository key, I get "key 1 import failed".  I tried this as part of the steps to install Logstash (https://www.elastic.co/guide/en/logstash/current/installing-logstash.html).  Following the same guide I was successful on Centos 8 and Fedora 35.  

Version-Release number of selected component (if applicable):
RPM version 4.16.1.3

How reproducible:
Every time

Steps to Reproduce:
1. Run the command: "sudo rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch"

Actual results:
error: https://artifacts.elastic.co/GPG-KEY-elasticsearch: key 1 import failed.

Expected results:
No error and key is successfully loaded.

Additional info:
Command was successful on Centos 8 (RPM 4.14.3) and Fedora 35 (RPM version 4.17.0) with no error.

This is due to openssl disabling SHA1 based signatures, see bug 2031742. The repo maintainer needs to update their key to use stronger crypto for it to continue working, in RHEL and elsewhere.

We could use some better diagnostics in for the case though.

*** Bug 2102539 has been marked as a duplicate of this bug. ***

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 (rpm bug fix and enhancement update), 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/RHBA-2022:8365