By default OpenNebula Debian images have systemd-networkd installed and enabled but if NETCFG_TYPE is not changed then the old /etc/network/interfaces is configured by context.
The issue is with Debian 12 (pre-release) where occurs the following problem:
May 26 02:57:42 localhost systemd[1]: Starting Wait for Network to be Configured...
May 26 02:59:43 localhost systemd-networkd-wait-online[961]: Timeout occurred while waiting for network connectivity.
May 26 02:59:43 localhost systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
May 26 02:59:43 localhost systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
May 26 02:59:43 localhost systemd[1]: Failed to start Wait for Network to be Configured.
This will delay the boot and contextualization.
There is a similar service NetworkManager-wait-online.service which does not hold the boot because it respects that no interface is managed by it.
Because the error does not happen in older Debian releases - I consider this a bug in Debian 12.
It may be fixed by explicitly enabling/disabling the relevant services for all used and unused netcfg types.
By default OpenNebula Debian images have
systemd-networkdinstalled and enabled but ifNETCFG_TYPEis not changed then the old/etc/network/interfacesis configured by context.The issue is with Debian 12 (pre-release) where occurs the following problem:
This will delay the boot and contextualization.
There is a similar service
NetworkManager-wait-online.servicewhich does not hold the boot because it respects that no interface is managed by it.Because the error does not happen in older Debian releases - I consider this a bug in Debian 12.
It may be fixed by explicitly enabling/disabling the relevant services for all used and unused netcfg types.