Bug 2084281

Summary: Useless 404 error when trying to upgrade to Fedora 36
Product: [Fedora] Fedora Reporter: Olivier Crête <olivier.crete>
Component: PackageKitAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: gnome-sig, jonathan, mcrha, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 17:58:41 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:
Attachments:
Description Flags
Screenshot of the error none

Description Olivier Crête 2022-05-11 19:05:17 UTC
Created attachment 1878745 [details]
Screenshot of the error

Description of problem:

From a fully up to date Fedora 35, I tried to upgrade to Fedora 36 through gnome-software.

I get a useless error about a 404 on some package. And no way to fix it through the UI.

I'm going to guess that the real error has nothing to do with packages missing and is some problem in my RPM db.

Version-Release number of selected component (if applicable):
gnome-software-41.5-1.fc35.x86_64

Comment 1 Olivier Crête 2022-05-11 19:11:14 UTC
I should mention that using the dnf system-upgrade plugin seems to work, so it's probably a packagekit/gnome-software issue.

Comment 2 Olivier Crête 2022-05-11 19:23:17 UTC
It seems that dnf tries to pull "selinux-policy-targeted-36.7-1.fc36.noarch.rpm", but packagekit tries to pull in the non-existing "selinux-policy-targeted;36.8-1.fc36;noarch;fedora"

I get the feeling that PackageKit is using the wrong package list?

I moved the bug to PackageKit to be more precise

Comment 3 Milan Crha 2022-05-12 05:40:58 UTC
Looking into bodhi the 36.8-1 went stable a week ago:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-47789bbc9d

It's correct that PackageKit picks it, it has an up-to-date data. I guess your mirror failed to get in sync with the Fedora content. I see similar errors when using dnf directly too, from time to time. There usually helps to re-try, when the dnf picks another mirror. I'm afraid the software cannot do much when the mirror is not in sync. The dnf does retry other mirrors, but I do not know how that works.

Comment 4 Ben Cotton 2022-11-29 18:54:16 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ben Cotton 2022-12-13 17:58:41 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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