MAAS

Bug #1970257
Comment #10

Comment 10 for bug 1970257

Revision history for this message

Alan Baghumian (alanbach) wrote on 2023-09-11:

#10

This bug was re-brought to my attention and I spent a little bit of testing time on it. I re-imported a packer-maas built RHEL 8 image, and performed a deployment using the custom partitioning script previously attached above. This issue is still happening with MAAS 3.3.

After the deployment, the machine fails to boot from GRUB due to the extra /boot/ prefix on the kernel and initrd paths. After manually removing /boot/ and pressing Ctrl+X to boot GRUB I was able to finally SSH to the machine as before.

Looking into the state of the machine I do confirm Jo's findings. GRUB is using /boot (UUID=75adced6-e475-4ef1-8530-de75be3f2707) as the root, hence the additional /boot/ in the loader files is throwing out the boot process:

[root@generic-4 boot]# grep -r 75adced6-e475-4ef1-8530-de75be *
efi/EFI/redhat/grub.cfg: search --no-floppy --fs-uuid --set=root --hint='hd0,gpt2' 75adced6-e475-4ef1-8530-de75be3f2707
efi/EFI/redhat/grub.cfg: search --no-floppy --fs-uuid --set=root 75adced6-e475-4ef1-8530-de75be3f2707
grub2/grub.cfg: search --no-floppy --fs-uuid --set=root --hint='hd0,gpt2' 75adced6-e475-4ef1-8530-de75be3f2707
grub2/grub.cfg: search --no-floppy --fs-uuid --set=root 75adced6-e475-4ef1-8530-de75be3f2707

[root@generic-4 boot]# blkid
/dev/vda1: SEC_TYPE="msdos" UUID="7D45-6317" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="9b53237b-e6fe-47b1-be1d-428e3372b53d"
/dev/vda2: UUID="75adced6-e475-4ef1-8530-de75be3f2707" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="cf3052a9-c4d3-4518-ab62-8aa64682f65c"
/dev/vda3: UUID="4b5a8ff1-c332-4afa-93d2-13a5d0e58088" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="a6b2ae3c-c29f-4a37-a210-f1a51a08df23"

[root@generic-4 boot]# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/vda3 during curtin installation
/dev/disk/by-uuid/4b5a8ff1-c332-4afa-93d2-13a5d0e58088 / xfs defaults 0 1
# /boot/ was on /dev/vda2 during curtin installation
/dev/disk/by-uuid/75adced6-e475-4ef1-8530-de75be3f2707 /boot/ xfs defaults 0 1
# /boot/efi was on /dev/vda1 during curtin installation
/dev/disk/by-uuid/7D45-6317 /boot/efi vfat defaults 0 1

Best,
Alan

[root@generic-4 boot]# grep -r 75adced6-e475-4ef1-8530-de75be *
efi/EFI/redhat/grub.cfg:  search --no-floppy --fs-uuid --set=root --hint='hd0,gpt2'  75adced6-e475-4ef1-8530-de75be3f2707
efi/EFI/redhat/grub.cfg:  search --no-floppy --fs-uuid --set=root 75adced6-e475-4ef1-8530-de75be3f2707
grub2/grub.cfg:  search --no-floppy --fs-uuid --set=root --hint='hd0,gpt2'  75adced6-e475-4ef1-8530-de75be3f2707
grub2/grub.cfg:  search --no-floppy --fs-uuid --set=root 75adced6-e475-4ef1-8530-de75be3f2707

[root@generic-4 boot]# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/vda3 during curtin installation
/dev/disk/by-uuid/4b5a8ff1-c332-4afa-93d2-13a5d0e58088 / xfs defaults 0 1
# /boot/ was on /dev/vda2 during curtin installation
/dev/disk/by-uuid/75adced6-e475-4ef1-8530-de75be3f2707 /boot/ xfs defaults 0 1
# /boot/efi was on /dev/vda1 during curtin installation
/dev/disk/by-uuid/7D45-6317 /boot/efi vfat defaults 0 1

Best,
Alan