Sunday, July 8, 2012

Fedora 17 : GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-17-i386

Today I tried to update my freshly upgraded Fedora 17 but it failed with the error:
GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386

On RPM Fusion I found the page with keys:

Downloaded the following key:
[get | view] (2011-10-28 21:34:45, 1.7 KB) [[attachment:RPM-GPG-KEY-rpmfusion-nonfree-fedora-17]]
...and moved it to /etc/pki/rpm-gpg/

Then I created a symbolic link to the key:
# ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-17 RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386

Finally I cleaned YUM and run update again:
# yum clean all
# yum check-update
# yum update
Is this ok [y/N]: y
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID d2382b83: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386
Importing GPG key 0xD2382B83:
 Userid     : "RPM Fusion nonfree repository for Fedora (17) "
 Fingerprint: 6edf 41e4 8312 dfd4 521b 78fb 0dd6 34bd d238 2b83
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-17-i386
Is this ok [y/N]: y
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction


  1. Thank you. I had a similar issue with F18 after I ran the F17 easylife script on F18. Went to the rpmfusion site and let the installer run the two rpms (for free and non-free IIRC) Now yum update is working again.

  2. after updatting i got a messafe like this:

    GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-18-i386

    how can i solve this issue?

  3. Same sentiment here. Thank you very much for the clean, concise (and best of all) correct instructions.

  4. Very clear and to the point. I used this approach for FC18 with slight modifications to the symlink and file names. (Why do we end up with these things to tweak sometimes? Oh well...). Grateful for the intelligent help!

  5. You can also just do yum --nogpgcheck to get around this issue. I know it's not the most secure choice, but it is a quick, dirty solution to the issue.