Bug 2069877

Summary: Uninformative error message on --import failure
Product: Red Hat Enterprise Linux 9 Reporter: Kyle Kinkaid <kkinkaid>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED ERRATA QA Contact: Jan Blazek <jblazek>
Severity: medium Docs Contact: Mariya Pershina <mpershin>
Priority: unspecified    
Version: CentOS StreamCC: bstinson, bugzilla, ffesti, jwboyer, mbanas, mdomonko, mpershin, pmatilai
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rpm-4.16.1.3-14.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 11:21:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kyle Kinkaid 2022-03-29 23:04:58 UTC
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.

Comment 1 Panu Matilainen 2022-03-30 10:08:43 UTC
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.

Comment 12 Florian Festi 2022-08-02 14:16:12 UTC
*** Bug 2102539 has been marked as a duplicate of this bug. ***

Comment 14 errata-xmlrpc 2022-11-15 11:21:17 UTC
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