Nothing in /etc/grub* is showing this UUID though - so it's more than probably a lack of update of the "menu".
This is especially true if we run a "grep -r UUID /etc/grub*" from within the image disk:
grub2.cfg: set kernelopts="root=UUID=81161d9c-88cf-4fc4-bf99-691bdcbcd3dc ro console=ttyS0,115200n8 no_timer_check crashkernel=auto "
grub2-efi.cfg: set kernelopts="root=UUID=81161d9c-88cf-4fc4-bf99-691bdcbcd3dc ro console=ttyS0,115200n8 no_timer_check crashkernel=auto "
Here, we can see the actual UUID it should use in the loader:
OK, that UUID is pointed in the boot options for the kernel, in grub:
loader/ entries/ 3096152462f947f eae105af3ba3df9 66-5.14. 0-43.el9. x86_64. conf:options root=UUID= 4a50018c- f6ea-4bd7- 95dc-badc49878c 01 ro console= ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=auto
Nothing in /etc/grub* is showing this UUID though - so it's more than probably a lack of update of the "menu".
This is especially true if we run a "grep -r UUID /etc/grub*" from within the image disk: "root=UUID= 81161d9c- 88cf-4fc4- bf99-691bdcbcd3 dc ro console= ttyS0,115200n8 no_timer_check crashkernel=auto " "root=UUID= 81161d9c- 88cf-4fc4- bf99-691bdcbcd3 dc ro console= ttyS0,115200n8 no_timer_check crashkernel=auto "
grub2.cfg: set kernelopts=
grub2-efi.cfg: set kernelopts=
Here, we can see the actual UUID it should use in the loader:
[virtuser@builder2 ~]$ virt-filesystems -a workload/ lab2-oc0- controller- 0.qcow2 --all --long --uuid -h 18-10-10- 26-00 88cf-4fc4- bf99-691bdcbcd3 dc
Name Type VFS Label MBR Size Parent UUID
/dev/sda1 filesystem vfat efi-part - 200M - 2180-0667
/dev/sda2 filesystem iso9660 config-2 - 378K - 2022-01-
/dev/sda3 filesystem xfs img-rootfs - 2.6G - 81161d9c-
/dev/sda1 partition - - - 200M /dev/sda -
/dev/sda2 partition - - - 1.0M /dev/sda -
/dev/sda3 partition - - - 99G /dev/sda -
/dev/sda device - - - 100G - -