Bug 1172349

Summary: 20=>21: Failing to import GPG Key for repository
Product: [Fedora] Fedora Reporter: Justin W. Flory (Fedora) <foss>
Component: fedupAssignee: Will Woods <wwoods>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: tflink, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-09 21:49:16 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 Justin W. Flory (Fedora) 2014-12-09 21:41:20 UTC
Description of problem:
On my Fedora 20 laptop, I updated my system and did a fresh install of fedup, only to run into an issue where it appears that fedup cannot complete the upgrade process because it fails to import the GPG key from the nonfree RPM Fusion repository.

I have tried deleting the file that it links that it says has no key, but even then, that did change anything.

My console output can be described here: http://ur1.ca/j2f3g

After failing to download the GPG key, the fedup tool terminates with reason of not installing any keys.

Version-Release number of selected component (if applicable):
0.9.0-2.fc20

How reproducible:
Every time

Steps to Reproduce:
1. Upgrade system using YUM and install fedup
2. Run: sudo fedup --network 21 --product=workstation
3. Successfully download all packages and a lot of data, but when importing GPG keys from RPM Fusion nonfree, fail to import the key and terminate.

Actual results:
Instant termination of fedup tool.

Expected results:
Successful upgrade to Fedora 21.

Additional info:
I started this upgrade process on a WiFi network with a heavy firewall, and at the time, I wondered if something was being blocked by the firewall that I needed. However, I am now on my home WiFi and I am experiencing the same issue that I was on the firewalled network.

Comment 1 Justin W. Flory (Fedora) 2014-12-09 21:49:16 UTC

*** This bug has been marked as a duplicate of bug 1066044 ***