[SOLVED] No bootable device : iPXE error after Ubuntu netboot installation

[garga]

Hi all,

I deploy and manage several Ubuntu 20.04 VMs using Ansible.

After few weeks, I needed to make a fresh install of some of these VMs. So I launch the script as usual and I get an infinite boot loop with a weird iXPE error that tells me that there is no device to boot.

I use the same script for months which simply fetches and deploys this image using a seed file.
http://archive.ubuntu.com/ubuntu/di.../current/legacy-images/netboot/netboot.tar.gz

I searched the web but I only find threads talking about custom tftpd servers. Nothing able to brings me some help.

I really don't know why I get this error now. Do you have any idea about what is going on ?

Thanks a lot.

Here is a VM config file :

cat /etc/pve/qemu-server/109.conf
acpi: 1
agent: 1
autostart: 0
balloon: 1024
boot: cnd
cores: 2
cpu: host,flags=+pcid;+spec-ctrl;+ssbd;+aes
cpuunits: 1024
kvm: 1
memory: 1024
name: kubedeploy
net0: virtio=,bridge=vmbr2,firewall=1
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=f2e4e08b-d359-4c64-ad4b-3e1202adaae1
sockets: 1
tablet: 0
template: 0
vga: qxl
virtio0: local-lvm:vm-109-disk-0,cache=writeback,discard=on,size=4G
vmgenid: f99e6fb1-63cc-44a1-a4ce-86ff3fa4349c

Here is the verbose output of my proxmox installation :

~# pveversion --verbose
proxmox-ve: 6.3-1 (running kernel: 5.4.101-1-pve)
pve-manager: 6.3-4 (running version: 6.3-4/0a38c56f)
pve-kernel-5.4: 6.3-6
pve-kernel-helper: 6.3-6
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.44-1-pve: 5.4.44-1
pve-kernel-4.15: 5.4-9
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-10-pve: 4.15.18-32
ceph-fuse: 12.2.13-pve1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-5
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-2
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve2

 

[garga]

Ok, I am dumb. There was must be a weird update somewhere since the last time I launch the script, but I now have to explicitly declare the boot order in the script otherwise net0 is the only booting device set in the boot order (hard disk is not checked by default)