Bug 1374852 - /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 missing from Fedora 23
Summary: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 missing from Fedora 23
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-repos
Version: 27
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedPreviousRelease
Depends On:
Blocks: F25BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2016-09-09 20:17 UTC by Adam Williamson
Modified: 2018-11-30 21:48 UTC (History)
10 users (show)

Fixed In Version: fedora-repos-23-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 21:48:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2016-09-09 20:17:36 UTC
Upgrades from Fedora 23 to Fedora 25 currently fail with an error:

Curl error (37): Couldn't read a file:/// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64]

it seems that this file is missing from Fedora 23's fedora-repos.

Proposing as a 'previous release' blocker for Fedora 25 Beta, as this violates "For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from fully updated installations of the last two stable Fedora releases with that package set installed." - https://fedoraproject.org/wiki/Fedora_25_Beta_Release_Criteria

Comment 1 Fedora Update System 2016-09-09 23:28:01 UTC
fedora-repos-23-2 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-772911949e

Comment 2 Fedora Update System 2016-09-11 05:22:35 UTC
fedora-repos-23-2 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-772911949e

Comment 3 Geoffrey Marr 2016-09-13 00:33:53 UTC
Discussed during the 2016-09-12 blocker review meeting: [1]

The decision to classify this bug as an AcceptedPreviousRelease bug breaks the upgrade path from Fedora 23 to Fedora 25. It violates the following criteria: 

"For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from fully updated installations of the last two stable Fedora releases with that package set installed."

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-09-12/f25-blocker-review.2016-09-12-16.01.txt

Comment 4 Fedora Update System 2016-09-14 01:18:38 UTC
fedora-repos-23-2 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Peter Ruan 2017-02-16 19:21:10 UTC
still seeing the problem when I tried to upgrdae f23 to f25 with the following command.

dnf system-upgrade download --refresh --releasever=25


warning: /var/lib/dnf/system-upgrade/kernel-core-4.8.6-300.fc25.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fdb19c98: NOKEY
Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64]
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.

Comment 6 Kevin Fenzi 2017-02-16 19:26:23 UTC
What version of fedora-repos do/did you have installed?

Comment 7 Bryan Yount 2017-04-11 17:50:09 UTC
(In reply to Kevin Fenzi from comment #6)
> What version of fedora-repos do/did you have installed?

Why can't DNF suggest updating fedora-repos when it encounters this error? This is not a user friendly error message.

Comment 8 Bryan Yount 2017-04-11 19:02:07 UTC
I actually opened Bug 1441350 to try to improve this error message in DNF in the future. Upgrading fedora-repos did resolve this RPM-GPG-KEY error on my system.

Comment 9 Adam Williamson 2017-04-11 19:11:50 UTC
Well, dnf is just a package manager. It's not Fedora-specific. It's already used by Fedora, RHEL, and CentOS, plus various smaller derivatives of them. So what should the message say "Please try updating fedora-repos, or rhel-repos, or centos-repos, or some other repos package"? Third party repos can also have key issues; should we teach dnf to recognize which repos are likely to be distro repos and which aren't?

Comment 10 Qiao Zhao 2017-06-28 13:29:26 UTC
Hi guys,

I met the same error when i try to upgrade my system from f23 to f26.
My command is: dnf system-upgrade download --refresh --releasever=26
Some log in here:

Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-x86_64 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-x86_64]
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.

And no /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-26-x86_64 file in my system.

Anybody can help? I didn't want to clean all download, it more than 1.5GB.

--
Thanks,
Qiao

Comment 11 Peter Robinson 2017-06-28 13:33:55 UTC
> I met the same error when i try to upgrade my system from f23 to f26.
> My command is: dnf system-upgrade download --refresh --releasever=26

Upgrade is only supported between two versions, so 23 -> 25 should work, but 23 -> 26 is not tested. You could manually import the f26 key before you try but it's not tested

Comment 12 Qiao Zhao 2017-06-28 14:02:18 UTC
(In reply to Peter Robinson from comment #11)
> > I met the same error when i try to upgrade my system from f23 to f26.
> > My command is: dnf system-upgrade download --refresh --releasever=26
> 
> Upgrade is only supported between two versions, so 23 -> 25 should work, but
> 23 -> 26 is not tested. You could manually import the f26 key before you try
> but it's not tested

Hi Peter,

Looks it works on my system.
I download a f26 key from https://getfedora.org/static/64DAB85D.txt,
and import this key, upgrade complete!

I will run 'dnf system-upgrade reboot' to start the upgrade. Hope everything is normal.

--
Thanks,
Qiao

Comment 13 Qiao Zhao 2017-06-30 07:24:17 UTC
Hi Peter,

My system works well now! When i run 'dnf system-upgrade reboot' before import fc26 key by manual, system update successful.
Thanks!

--
Thanks,
Qiao

Comment 14 Matt Moldvan 2017-11-20 03:41:14 UTC
Happened to me just now upgrading from 25 to 26:

Total                                               641 kB/s | 1.2 GB     31:42     
warning: /var/lib/dnf/system-upgrade/xorg-x11-drv-nouveau-1.0.15-1.fc26.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 64dab85d: NOKEY
Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-26-x86_64 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-26-x86_64]

Comment 15 Jan Kurik 2018-05-31 09:06:05 UTC
This bug is currently reported against a Fedora version which is already unsuported.
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

Comment 16 Ben Cotton 2018-11-27 15:22:20 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 17 Ben Cotton 2018-11-30 21:48:35 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.


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