Ubuntu 26.04 (resolute) Failed to start systemd-networkd-wait-online.service

V

VanishingEntropy

New Member
Apr 8, 2025
6
1
3
I am using the Ubuntu 26.04 cloud image and a cloud-init file.

In the boot log I can see:

Code: 
[   10.049073] cloud-init[1330]: 2026-04-23 20:23:43,826 - net[WARNING]: Unable to rename interfaces: [['bc:24:11:38:78:9e', 'eth0', None, None]] due to errors: ['[busy] Error renaming mac=bc:24:11:38:78:9e from ens18 to eth0']
[   10.053305] cloud-init[1330]: 2026-04-23 20:23:43,826 - stages.py[WARNING]: Failed to rename devices: Failed to apply network config names: [busy] Error renaming mac=bc:24:11:38:78:9e from ens18 to eth0

Code: 
root@test-26:~# systemctl status systemd-networkd-wait-online.service
× systemd-networkd-wait-online.service - Wait for Network to be Online
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd-wait-online.service; enabled; preset: enabled)
    Drop-In: /run/systemd/generator.late/systemd-networkd-wait-online.service.d
             └─10-netplan.conf
     Active: failed (Result: exit-code) since Thu 2026-04-23 20:25:45 UTC; 2min 6s ago
 Invocation: 8b4bd530d1bc4092b9b4cd98aca70d8d
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 1397 ExecStart=/lib/systemd/systemd-networkd-wait-online -i eth0:degraded (code=exited, status=1/FAILURE)
   Main PID: 1397 (code=exited, status=1/FAILURE)
   Mem peak: 2M
        CPU: 13ms

Apr 23 20:23:43 ubuntu systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Online...
Apr 23 20:25:45 test-26 systemd-networkd-wait-online[1397]: Timeout occurred while waiting for network connectivity.
Apr 23 20:25:45 test-26 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 20:25:45 test-26 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Apr 23 20:25:45 test-26 systemd[1]: Failed to start systemd-networkd-wait-online.service - Wait for Network to be Online.
root@test-26:~# cat /etc/netplan/50-cloud-init.yaml
network:
  version: 2
  ethernets:
    eth0:
      match:
        macaddress: "bc:24:11:38:78:9e"
      dhcp4: true
      set-name: "eth0"
 
It might be useful if in the cloud-init config could specify the interface name. Unsure though.

On the second boot I don't get the error but I do get strangeness.

In the boot log I see:
Code: 
[    8.024866] cloud-init[1323]: Cloud-init v. 26.1-0ubuntu2 running 'init' at Fri, 24 Apr 2026 14:59:13 +0000. Up 8.01 seconds.
[    8.036124] cloud-init[1323]: ci-info: +++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++
[    8.039187] cloud-init[1323]: ci-info: +--------+------+------------------------------+---------------+--------+-------------------+
[    8.042591] cloud-init[1323]: ci-info: | Device |  Up  |           Address            |      Mask     | Scope  |     Hw-Address    |
[    8.045873] cloud-init[1323]: ci-info: +--------+------+------------------------------+---------------+--------+-------------------+
[    8.049218] cloud-init[1323]: ci-info: |  eth0  | True |        192.168.1.108         | 255.255.255.0 | global | bc:24:11:38:78:9e |
[    8.052591] cloud-init[1323]: ci-info: |  eth0  | True | fe80::be24:11ff:fe38:789e/64 |       .       |  link  | bc:24:11:38:78:9e |
[    8.056095] cloud-init[1323]: ci-info: |   lo   | True |          127.0.0.1           |   255.0.0.0   |  host  |         .         |
[    8.059255] cloud-init[1323]: ci-info: |   lo   | True |           ::1/128            |       .       |  host  |         .         |
[    8.062527] cloud-init[1323]: ci-info: +--------+------+------------------------------+---------------+--------+-------------------+

Which says the IP address is 192.168.1.108. But when everything is finished it actually gets a different IP address. In my current boot it became 192.168.1.111.

I notice in the DHCP server logs it assigns 192.168.1.108 for the MAC address without the host name. And then it assigns 192.168.1.111 for the MAC address + the host host-name.

I'm assuming this is more of an OS issue than a Proxmox issue.
 
You must log in or register to reply here.
Top Bottom
Back