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

When using the image-builder Azure RHEL-8.10 image to leapp upgrade to 9.6, after upgrade and reboot, the default kernel cannot be switched to vmlinuz-upgrade. Still boot up from RHEL-8 kernel.
 

• It only happened in the image-builder Azure image(e.g. http://download.eng.bos.redhat.com/rhel-8/composes/RHEL-8/RHEL-8.10.0-updates-20241210.2/compose/BaseOS/x86_64/images/rhel-azure-8.10-1574.x86_64.vhd.xz) but not in the Azure Marketplace RHEL-8.8 ARM image.
• Check with "grubby --default-kernel" can see the default kernel is:

  [root@wala810imagebuilder212180610-vm1 ~]# grubby --default-kernel
  /boot/vmlinuz-upgrade.aarch64

• No such issue in x86_64
• If only upgrade a kernel in this image, it can switch to the new kernel after reboot.
   
  After upgrade, the grubby entries:

  [root@wala810imagebuilder212180610-vm1 ~]# grubby --info=ALL
  index=0
  kernel="/boot/vmlinuz-upgrade.aarch64"
  args="ro loglevel=3 crashkernel=auto console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 $tuned_params enforcing=0 net.naming-scheme=rhel-8.0 plymouth.enable=0 rd.plymouth=0"
  root="UUID=34e5810b-6234-4c8c-a38b-dd1429c64e04"
  initrd="/boot/initramfs-upgrade.aarch64.img"
  title="RHEL-Upgrade-Initramfs"
  id="95e62baa24e04a139259f8f3c650712b-upgrade.aarch64"
  index=1
  kernel="/boot/vmlinuz-4.18.0-553.30.1.el8_10.aarch64"
  args="ro loglevel=3 crashkernel=auto console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 $tuned_params"
  root="UUID=34e5810b-6234-4c8c-a38b-dd1429c64e04"
  initrd="/boot/initramfs-4.18.0-553.30.1.el8_10.aarch64.img $tuned_initrd"
  title="Red Hat Enterprise Linux (4.18.0-553.30.1.el8_10.aarch64) 8.10 (Ootpa)"
  id="ffffffffffffffffffffffffffffffff-4.18.0-553.30.1.el8_10.aarch64"

  [root@wala810imagebuilder212180610-vm1 ~]# cat /proc/cmdline 
  BOOT_IMAGE=(hd0,gpt2)/vmlinuz-4.18.0-553.30.1.el8_10.aarch64 root=UUID=34e5810b-6234-4c8c-a38b-dd1429c64e04 ro loglevel=3 crashkernel=auto console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 

  [root@wala810imagebuilder212180610-vm1 ~]# cat /proc/cmdline 
  BOOT_IMAGE=(hd0,gpt2)/vmlinuz-4.18.0-553.30.1.el8_10.aarch64 root=UUID=34e5810b-6234-4c8c-a38b-dd1429c64e04 ro loglevel=3 crashkernel=auto console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300
  [root@wala810imagebuilder212180610-vm1 ~]# cat /etc/default/grub 
  GRUB_CMDLINE_LINUX="ro loglevel=3 crashkernel=auto console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300"
  GRUB_TIMEOUT=10
  GRUB_ENABLE_BLSCFG=true
  GRUB_DISABLE_RECOVERY=true
  GRUB_DISABLE_SUBMENU=true
  GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
  GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"
  GRUB_TERMINAL="serial console"
  GRUB_TIMEOUT_STYLE=countdown
  GRUB_DEFAULT=saved 

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

  rhel-azure-8.10-1574.x86_64.vhd.xz
  kernel-4.18.0-553.30.1.el8_10.aarch64
  leapp-deps-0.18.0-2.el8_10.noarch
  leapp-upgrade-el8toel9-deps-0.21.0-4.el8_10.noarch
  python3-leapp-0.18.0-2.el8_10.noarch
  leapp-upgrade-el8toel9-0.21.0-4.el8_10.noarch
  leapp-0.18.0-2.el8_10.noarch
  snactor-0.18.0-2.el8_10.noarch
   
  grub2-tools-extra-2.02-160.el8_10.aarch64
  grub2-tools-2.02-160.el8_10.aarch64
  grub2-common-2.02-160.el8_10.noarch
  grub2-tools-minimal-2.02-160.el8_10.aarch64
  grubby-8.40-49.el8.aarch64
  grub2-efi-aa64-2.02-160.el8_10.aarch64

  How reproducible is this bug?:

  100%

  Steps to reproduce

1. Download a RHEL-8.10 image from internal repo. Install leapp packages, stop firewalld service, unload qla4xxx module, prepare leapp upgrade repo.
2. leapp upgrade --debug --no-rhsm
3. reboot

Expected results

Boot up from vmlinuz-upgrade after reboot

Actual results

Still boot up from RHEL-8 kernel