[Bug 2107575] Re: Offline install results in empty /etc/netplan, which stalls boot for 2min+

[Nick Rosbrook]

I thought this was something we covered in the noble cycle's rework of
wait-online.

@lukas, isn't this the purpose of:

[Unit]
ConditionPathIsSymbolicLink=/run/systemd/generator/network-online.target.wants/systemd-networkd-wait-online.service

netplan should only create that symlink if it generates a valid config?
If not, the symlink won't be present, and then the unit would be
skipped.

That's obviously *not* working here, but I thought those were the
desired semantics.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

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

Title:
  Offline install results in empty /etc/netplan, which stalls boot for
  2min+

Status in subiquity:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I did an offline install of plucky 25.04 server on a laptop. I
  unplugged the network cable, and didn't configure wifi.

  The installation finished, but first boot, and subsequent boots, were
  delayed by 2min+, waiting on systemd-networkd-wait-online.service.

  Further inspection showed that /etc/netplan was completely empty. Not
  surprising to me, as no network was configured during installation,
  but having the system still waiting for a network in this case was
  surprising.

  Creating the following file in /etc/netplan made boot fast again:

  $ cat /etc/netplan/01.yaml
  network:
    version: 2
    ethernets:
      <nic-name>:
        optional: true

  This looks similar to
  https://bugs.launchpad.net/subiquity/+bug/2063331, but I opted to file
  a new bug because that one is "fix committed", and the user did
  configure one nic at least in that bug.

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