Bug 1393586 - Failure of yum with GPG keys in /var/lib/rpm/pubkeys
Summary: Failure of yum with GPG keys in /var/lib/rpm/pubkeys
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpm
Version: 7.3
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Florian Festi
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1630909
TreeView+ depends on / blocked
 
Reported: 2016-11-09 22:31 UTC by Zailo Leite
Modified: 2019-10-15 07:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-15 07:43:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Zailo Leite 2016-11-09 22:31:05 UTC
Description of problem:

When using the /var/lib/rpm/pubkeys directory to store the GPG keys, there needs to be at least one gpg key in the rpmdb database. If no keys are in and keys are deployed in /var/lib/rpm/pubkeys any operations will return:

%%%%%%%%%%%
You have enabled checking of packages via GPG keys. This is a good thing. 
However, you do not have any GPG public keys installed. You need to download
the keys for packages you wish to install and install them.
You can do that by running the command:
    rpm --import public.gpg.key
%%%%%%%%%%%

And any attempts to import a key will fail silently. It is necessary to remove theGPG files in /var/lib/rpm/pubkeys and then add one key with rpm --import, which then succeeds. The key files can then be added back to /var/lib/rpm/pubkeys and all works as expected.

How reproducible:


Steps to Reproduce:
1. delete all gpg-pubkey-* entries from rpmdb
2. Add GPG key files in /var/lib/rpm/pubkeys
3. Attempt yum install / Attempt to rpm --inport GPG key

Actual results:
Failure to import GPG key and requirement to use --nogpg on yum operations.

Expected results:
Nominal operation on yum and rpm.

Additional info:

Comment 9 Daniel Mach 2019-10-15 07:43:25 UTC
There is no plan to fix this bug during RHEL 7 life cycle.
If you still consider the issue important, please contact your support
representative.


Note You need to log in before you can comment on or make changes to this bug.