Comment 4 for bug 1988773

I've encountered a similar issue when using Jammy with autoinstall on a DHCP-enabled network. In my case, I was able to resolve the issue by adding 'network-config=disabled' as a boot parameter to prevent cloud-init from interfering with the network configuration.

Update: Scratch that, even with the "network-config=disabled" boot parameter, the installer occasionally encounters the same issue. I can confirm that this happens intermittently on installations with a network configuration that includes a bridge, as shown below:

network:
  bridges:
    br0:
      addresses:
        - 192.168.1.2/24
      routes:
        - to: default
          via: 192.168.1.1
      interfaces:
        - eth0
      link-local: []
      nameservers:
        addresses:
          - 8.8.8.8
          - 8.8.4.4
        search:
          - example.com
  ethernets:
    eth0:
      dhcp4: false
      dhcp6: false
  version: 2

However, the issue does not occur on setups like this:

network:
  ethernets:
    eth0:
      addresses:
        - 192.168.1.2/24
      routes:
        - to: default
          via: 192.168.1.1
      nameservers:
        addresses:
          - 8.8.8.8
          - 8.8.4.4
        search:
          - example.com
  version: 2