What were you trying to do that didn't work?

Select a previous working kernel in the grub menu after auto-updating to an unbootable / broken system with bootc.

What is the impact of this issue to you?

Without this I have to throw the system away and create a new one, greenboot doesn't rollback either RHEL-61158 If I have to do this manually for each auto-updated system that was broken that's a lot of time to fix it.

Please provide the package NVR for which the bug is seen:

 
grub2-common-2.06-92.el9.noarch

How reproducible is this bug?:

100%

Steps to reproduce

1. Create a qcow2 image from the container image

   cat config.toml
    [[customizations.user]]
   name = "alice"
   password = "bob"
   groups = ["wheel"]
   

   podman run     --rm     -it     --privileged     --pull=newer     --security-opt label=type:unconfined_t     -v $(pwd)/config.toml:/config.toml:ro     -v $(pwd)/output:/output     quay.io/centos-bootc/bootc-image-builder:latest     --type qcow2     quay.io/centos-bootc/centos-bootc:stream9

2. Boot the VM

   # qemu-img convert -f qcow2 -O qcow2 -o lazy_refcounts=on output/qcow2/disk.qcow2 /var/lib/libvirt/images/stream9.qcow2
   # virt-install --import --disk /var/lib/libvirt/images/stream9.qcow2 --memory 2048 --vcpus 2 --nographics --os-variant rhel-unknown --watchdog i6300esb

   Expected results

The boot menu is shown. I can select which entry I want to boot.

Actual results

The system boots, the boot menu is not shown.

Additional info

I tried to hit Shift, a character key or the ESC key to force display the GRUB menu, to no avail. I can't update the current Grub config because of https://bugzilla.redhat.com/show_bug.cgi?id=2308594
I confirmed that grub2 is available
This also can be observed with bootc installations
I can't get into the boot menu on the cloud image either, from https://cloud.centos.org/centos/9-stream/x86_64/images/, CentOS-Stream-GenericCloud-x86_64-9-20240930.0.x86_64.qcow2