1, install f43 2, sudo dnf upgrade --refresh 3, reboot 4, sudo dnf system-upgrade download --releasever=44 5, dnf5 offline reboot wait a while there is : root@localhost-live:~# cat /etc/fedora-release Fedora release 44 (Forty Four) BUT root@localhost-live:~# grubby --default-kernel /boot/vmlinuz-6.19.9-200.fc43.x86_64 root@localhost-live:~# uname -a Linux localhost-live 6.19.9-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Mar 19 21:34:56 UTC 2026 x86_64 GNU/Linux root@localhost-live:~# rpm -q rpm rpm-6.0.1-2.fc44.x86_64 root@localhost-live:~# rpm -q kernel kernel-6.17.1-300.fc43.x86_64 kernel-6.19.9-200.fc43.x86_64 kernel-6.19.8-300.fc44.x86_64 Reproducible: Always
its probably due to the fact that kernel-6.19.9-200.fc43.x86_64 is higher
Proposed as a Blocker for 44-final by Fedora user psklenar using the blocker tracking app because: f43 upgrade to f44 processed without any issue. But after the reboot - default kernel is from fedora 43.
I don't think this actually violates any criteria, if the system works. It's also probably resolved right now, because https://bodhi.fedoraproject.org/updates/FEDORA-2026-1f3a3ab9fa went stable. If https://bodhi.fedoraproject.org/updates/FEDORA-2026-d4572d6000 goes stable before https://bodhi.fedoraproject.org/updates/FEDORA-2026-e976c4f5fa , it'd probably happen again. But yeah, I don't think it's really a *problem* per se.
F44 and F43 (and F42) always have the same kernel versions unless you happen to upgrade during a freeze. I am guessing you installed 6.19.9 while it was in updates testing, and did the upgrade before it was promoted to stable. This is expected behavior and not a bug. If you are dealing with stable repositories, they should typically be in sync. F44 kernels are -300 for the 6.19.x series, so it should be an upgrade for all earlier releases.