Bug 1388887

Summary: Invalid repositories break offline updates without visible error message
Product: [Fedora] Fedora Reporter: Thomas Wright <tom.tdw>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: jonathan, klember, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:47:52 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:
Attachments:
Description Flags
An example of a RPM repo triggering this bug none

Description Thomas Wright 2016-10-26 11:21:00 UTC 
Description of problem:
Any invalid repositories in /etc/yum.repos.d will cause offline updates (as triggered within gnome software) to fail silently. It looks like during the offline update packagekit is using curl to attempt to retrieve the public key of the repo -- this was never going to work as the machine is not even connected to the internet when installing offline updates. The following error message can be retrieved manually from packagekit after the update,
[root@localhost twright]# pkcon offline-status
Status:	Failed
ErrorCode:failed-initialization
ErrorDetails:Curl error (6): Couldn't resolve host name for https://copr-be.cloud.fedoraproject.org/results/zyga/snapcore/pubkey.gpg [Could not resolve host: copr-be.cloud.fedoraproject.org]

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. Add a repo that cannot be reached to /etc/yum.repos.d
2. Trigger an offline update from gnome software (or with sudo pkcon offline-trigger)

Actual results:
Update fails silently, and upon opening gnome software, you are still prompted to restart to install updates.

Expected results:
Updates apply normally, despite missing repos. The fact that extra repos which cannot be reached should not disrupt the offline update as the packages for this have 

Additional info:
Tested on both Fedora 25 and Fedora 24 with the same result.
Comment 1 Thomas Wright 2016-10-26 11:24:39 UTC 
Created attachment 1214260 [details]
An example of a RPM repo triggering this bug
Comment 2 Fedora End Of Life 2017-11-16 19:20:09 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2017-12-12 10:47:52 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.