Debian Image not being deployed

[Joao Paulo]

Hi all,

As per the following thread: https://discourse.maas.io/t/debian-not-deploying/7712

I am using the latest Maas version (3.4) with Ubuntu 20.04 LTS (the default) as the comissioning distro.
I tried to follow the instructions present at https://github.com/canonical/packer-maas/tree/main/debian but until now I have been unsuccessful to launch a Debian 12 Machine.

Server Specs:
HP DL380 Gen 10+ with EFI enabled

My commands for the image generation:

git clone https://github.com/canonical/packer-maas.git
cd packer-maas/debian/
make debian SERIES=bookworm
sudo cp curtin_userdata_custom_amd64 /var/snap/maas/current/preseeds/curtin_userdata_custom_amd64_generic_debian-12
maas admin $PROFILE boot-resources create name='custom/debian-12' title='Debian 12 Custom' architecture='amd64/generic' filetype='tgz' content@=debian-custom-cloudimg.tar.gz -k

The error after trying the deploy on MaaS (checked at Logs->Event Logs)
HTTP Request - /images/custom/amd64/ga-20.04/debian-12/no-such-image/boot-kernel
Marking node failed - Missing boot image custom/amd64/ga-20.04/debian-12.

Thanks a lot
BR

[Jacopo Rota (r00ta)]

managed to reproduce locally.
The ephemeral image to install debian is fetched properly

```
2023-12-15 15:10:42 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 172.0.2.7
2023-12-15 15:10:42 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 172.0.2.7
2023-12-15 15:10:43 provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/command.lst requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/fs.lst requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/crypto.lst requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/terminal.lst requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg-40:01:7a:cb:80:ac requested by 172.0.2.7
2023-12-15 15:10:45 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/boot-kernel requested by 172.0.2.7
2023-12-15 15:10:46 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/boot-initrd requested by 172.0.2.7
2023-12-15 15:11:01 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/squashfs requested by 172.0.2.7
2023-12-15 15:12:04 provisioningserver.rackdservices.http: [info] /images/custom/amd64/generic/debian-12/uploaded/root-tgz requested by 172.0.2.7
```

but then when the machine reboots the grub configuration returned by MAAS is wrong
```
$ curl localhost:5248/grub/grub.cfg-40:01:7a:cb:80:ac
set default="0"
set timeout=0

menuentry 'Ephemeral' {
    echo 'Booting under MAAS direction...'
    linux /images/custom/amd64/ga-20.04/debian-12/no-such-image/boot-kernel nomodeset ro root=squash:http://127.0.0.1:5248/images/custom/amd64/ga-20.04/debian-12/no-such-image/squashfs ip=::::ciscom4:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:\{'datasource_list': ['MAAS']\}end_cc cloud-config-url=http://127.0.0.1:5248/MAAS/metadata/latest/by-id/cqs6rd/?op=get_preseed log_host=127.0.0.1 log_port=5247 --- BOOTIF=01-${net_default_mac}
    initrd /images/custom/amd64/ga-20.04/debian-12/no-such-image/boot-initrd
}
```

It should return the config to boot from the local disk instead
```
set default="0"
set timeout=0

menuentry 'Local' {
    echo 'Booting local disk...'
    # The bootloader paths list for secure boot is shortened because of LP:2022084
    for bootloader in \
            boot/bootx64.efi \
            ubuntu/shimx64.efi \
            ubuntu/grubx64.efi \
            Microsoft/Boot/bootmgfw.efi; do
        search --set=root --file /efi/$bootloader
        if [ $? -eq 0 ]; then
            chainloader /efi/$bootloader
            boot
        fi
    done

    if [ "${shim_lock}" != "y" ]; then
        echo 'Secure boot is disabled, trying chainloader...'
        for bootloader in \
                centos/shimx64.efi \
                ce...

[Jack Lloyd-Walters (lloydwaltersj)]

Just chiming in to say the same issue also occurs for the new alma images

[Scott Storck (scttstrck)]

I have the same problem with a Ubuntu custom image:
HTTP Request - /images/custom/amd64/ga-22.04/custom-jammy/no-such-image/boot-kernel
Marking node failed - Missing boot image custom/amd64/ga-22.04/custom-jammy.

I create the image the same way and have the exact same problems.