[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

[Chad Smith]

Thanks Lukas: +1 on this changeset not degrading early boot install
scenarios  where systemd services are ordered After=systemd-networkd-
wait-online.service

Preliminary testing on Azure platform look good with accelerated networking enabled have confirmed dual-nic tests correctly configure the primary network devices brought  and blocking systemd-networkd-wait-online awaiting the matching hv_netsvc devices.
The tests confirm systemd-networkd-wait-online.service properly awaits the individual devices Also, initial cloud-init integration test runs on Azure noble w/ netplan.io v.1.0-2ubuntu1 do not seem to expose any regressions for our integration tests so far. 

cloud-init Ec2 testing of this same proposed netplan.io package doesn't
show any degradation of behavior in detecting Ec2's IMDS in early boot.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311

Title:
  Setting "optional: true" to overcome he timeout "Job systemd-networkd-
  wait-online" does no longer work with latest noble image

Status in Netplan:
  In Progress
Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Noble:
  Fix Committed
Status in systemd source package in Noble:
  Invalid

Bug description:
  Especially on s390x (but not limited to s390x) it's often the case that a system has network devices that are not necessarily connected during boot-up and one gets such a 2 min timeout:
  "Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"

  In the past I could avoid that by setting "optional: true" post-install (no perfect, but worked),
  but this does no longer seem to work using the latest noble ISO image (Apr 5th).

  Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
  this for me:

  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
      ethernets:
          enP1p0s0:
              optional: true
              dhcp4: true
          enP1p0s0d1:
              optional: true
              dhcp4: true
          enP2p0s0:
              optional: true
              dhcp4: true
          enP2p0s0d1:
              optional: true
              dhcp4: true
          encc000: {}
      version: 2
      vlans:
          encc000.2653:
              addresses:
              - 10.11.12.15/24
              gateway4: 10.11.12.1
              id: 2653
              link: encc000
              nameservers:
                  addresses:
                  - 10.11.12.1

  ... can be set fine (also --dry-run does not moan, except about
  dhcp4).

  This worked in the past on noble, but also on older Ubuntu releases
  like jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions