I'm glad to see I'm not the only one with this problem. I have not had this problem before since I use /etc/dnf/dnf.conf to block kernel updates to prevent spamming /boot with every minor update. Until yesterday my running kernel was 5.0.7-200.fc29.x86_64 I intended to upgrade from Fed29 to Fed30 , so removed the block and ran dnf update. I ran the dnf upgrade-plugin but when I rebooted I noticed the kernel did not change. After some checking I dnf remove kernel kernel-core then dnf install kernel. This produced the kernel image in /boot and the entry in /sys/lib/modules ( the kernel modules dep got pulled in too ) but the time stamp of /boot/grub2/grub.conf had not changed. As OP, I grub2-mkconfig -o /boot/grub/grub2.cfg , this did work and I can now boot to the new kernel. The system fails to finish the Fed30 upgrade and I suspect that is a corollary of this bug. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx