Bug 2463747

Summary: Fedora 43 to 44 upgrade via Discover fails due to missing network
Product: [Fedora] Fedora Reporter: Janne Grunau <janne-fdr>
Component: PackageKitAssignee: Neal Gompa <ngompa13>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 44CC: ales.astone, asahi-sig, davide, gnome-sig, kde-sig, ngompa13, rhughes
Target Milestone: ---Keywords: Upgrades
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: PackageKit-1.4.0-3.fc45 PackageKit-1.4.0-3.fc44 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-11-12 02:32:20 UTC Type: ---
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
PackageKit / NetworkManager log excerpt of failed update
none
F44 to F45 pk-offline-upgrade excerpt still showing the same issue
none
F44 to F45 pk-offline-upgrade with verbose packagekitd
none
Patch to avoid repo metadata expiration when online none

Description Janne Grunau 2026-04-29 08:53:19 UTC
The update to Fedora 44 on a Fedora Asahi Remix Mac Studio fails due to PackageKit trying to access repositories before the network is up.

Reproducible: Always

Steps to Reproduce:
1. Update to Fedora 44 in Discover
2. reboot and install updates
3. Update starts but errors immediately and reboots
4. after login a failed offline update is reported due 
Actual Results:
A failed offline update is reported:
`Failed to download metadata (baseurl: “Index of /results/@asahi/u-boot/fedora-44-aarch64/”) for repository “copr:copr.fedorainfracloud.org:group_asahi:u-boot”: Usable URL not found`
The failing repository is random and unrelated to the error

Expected Results:
System updated to Fedora 44

Comment 1 Janne Grunau 2026-04-29 08:54:35 UTC
Created attachment 2138565 [details]
PackageKit / NetworkManager log excerpt of failed update

Comment 2 Janne Grunau 2026-11-03 11:06:26 UTC
Created attachment 2162811 [details]
F44 to F45 pk-offline-upgrade excerpt still showing the same issue

problem persists for F44 to F45 system-upgrades

Comment 3 Janne Grunau 2026-11-03 13:44:43 UTC
Created attachment 2162820 [details]
F44 to F45 pk-offline-upgrade with verbose packagekitd

PackageKit decides for some reason to expire the F45 repository data although it is in cache-only mode

| Nov 03 14:36:54 packagekitd[852]: 14:36:54        PackageKit-DNF5        Setting cache-only mode (offline)
| Nov 03 14:36:54 pk-offline-update[842]: status refresh-cache
| Nov 03 14:36:54 packagekitd[852]: 14:36:54        PackageKit-DNF5        Using cachedir: /var/cache/PackageKit/45/metadata
| Nov 03 14:36:54 packagekitd[852]: 14:36:54        PackageKit-DNF5        Expiring repository metadata: updates

Comment 4 Janne Grunau 2026-11-03 15:26:48 UTC
Created attachment 2162838 [details]
Patch to avoid repo metadata expiration when online

system-upgrade succeeded with attached patch against PackageKit-0:1.4.0-2.fc44

I think it's unfortunately not correct. pk_backend_is_online() queries the actual network state and not whether the transaction is online or not. From a cursory look the backend doesn't know if a transaction is is supposed to run online or offline.

Comment 5 Aoife Moloney 2026-11-10 19:44:45 UTC
This message is a reminder that Fedora Linux 43 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 43 on 2026-12-02.
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 '43'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 43 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 6 Janne Grunau 2026-11-10 20:12:28 UTC
The issue reproduces in Fedora 44 to Fedora 45 system upgrades, version adjusted

Comment 7 Fedora Update System 2026-11-11 17:56:44 UTC
FEDORA-2026-708d43b08c (fedora-appstream-metadata-20261002-2.fc44 and PackageKit-1.4.0-3.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-708d43b08c

Comment 8 Fedora Update System 2026-11-11 17:56:45 UTC
FEDORA-2026-a78aec7d06 (fedora-appstream-metadata-20261002-2.fc45 and PackageKit-1.4.0-3.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a78aec7d06

Comment 9 Fedora Update System 2026-11-12 02:32:20 UTC
FEDORA-2026-a78aec7d06 (fedora-appstream-metadata-20261002-2.fc45 and PackageKit-1.4.0-3.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2026-11-12 02:52:14 UTC
FEDORA-2026-708d43b08c (fedora-appstream-metadata-20261002-2.fc44 and PackageKit-1.4.0-3.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.