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:
rpm exit with 0 even if key import fail

Version-Release number of selected component (if applicable):
rpm-4.8.0-30.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.
# gpg --gen-key
---%<----------
# gpg -k
/root/.gnupg/pubring.gpg
------------------------
pub   2048R/EF271BD7 2012-10-24
uid                  tester <test@test>
sub   2048R/EB178E96 2012-10-24

2.
# gpg --output key.exp --export 
# gpg -a --export > key.exp.txt
# touch key.0
# echo 'dwionfd39feuwqfie' > key.ascii

3.
# rpm --import key.exp ; echo $?
0
# rpm -qa gpg-pubkey*
# rpm --import key.0 ; echo $?
error: key.0: import read failed(0).
1
# rpm --import /bin/bash ; echo $?
0
# rpm --import key.ascii ; echo $?
error: key.ascii: import read failed(0).
1
# rpm --import key.exp.txt ; echo $?
0
# rpm -qa gpg-pubkey*
gpg-pubkey-ef271bd7-5087ef29

  
Actual results:
When the key cannot be exported from a file no error is returned.

Expected results:

On RHEL5 this works as expected; therefore this bug can be considered as regression.

rhel58# rpm --import key.exp ; echo $?
error: key.exp: import read failed(-1).
1
#

Additional info:

This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0461.html