TL;DR question: previous build for the same version made new kernel unbootable, is this a known issue/fixed now?
I notice that this obsoleted FEDORA-2019-cadb2ea4bf. I accidentally had that earlier one installed, together with a kernel update, in the same dnf update --enablerepo=updates-testing --security transaction. The new kernel version was unbootable (missing modules it seems).
I booted into an older kernel, noticed that new kernel wasn't really fully installed (one of the kernel-* packages was not listing as installed for that version, forget which).distro-synced grub back to 2.02-84, deleted the (partially installed) new kernel, rebooted again, installed the new kernel, and this time all looks normal, new kernel version is bootable.
This update has been submitted for testing by javierm.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted grub2-2.02-85.fc30, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
TL;DR question: previous build for the same version made new kernel unbootable, is this a known issue/fixed now?
I notice that this obsoleted FEDORA-2019-cadb2ea4bf. I accidentally had that earlier one installed, together with a kernel update, in the same
dnf update --enablerepo=updates-testing --securitytransaction. The new kernel version was unbootable (missing modules it seems).I booted into an older kernel, noticed that new kernel wasn't really fully installed (one of the
kernel-*packages was not listing as installed for that version, forget which).distro-syncedgrubback to 2.02-84, deleted the (partially installed) new kernel, rebooted again, installed the new kernel, and this time all looks normal, new kernel version is bootable.This update has been pushed to testing.
This update has been obsoleted by grub2-2.02-87.fc30.