Hi Lukas,
I tested the package in your ppa with following configuration:
```
network:
ethernets:
all:
dhcp4: true
match:
name: e*
optional: true
version: 2
```
With the version `1.0-2build1` it hit the timeout even though I set all
the interfaces on my DUT(arm64) optional.
Here is the log of journalctl for relevant occurance:
```
Apr 16 11:47:11 kria systemd[1]: Starting systemd-networkd-wait-online.service
- Wait for Network to be Configured...
Apr 16 11:49:11 kria systemd-networkd-wait-online[1055]: Timeout occurred while
waiting for network connectivity.
Apr 16 11:49:11 kria systemd[1]: systemd-networkd-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Apr 16 11:49:11 kria systemd[1]: systemd-networkd-wait-online.service: Failed
with result 'exit-code'.
Apr 16 11:49:11 kria systemd[1]: Failed to start
systemd-networkd-wait-online.service - Wait for Network to be Configured.
```
But after installing the version `1.0-2ubuntu1~ppa3`,
`systemd-networkd-wait-online` is not triggered since all interfaces set to
optional. Therefore no timeout
```
ubuntu@kria:~$ apt policy netplan.io
netplan.io:
Installed: 1.0-2ubuntu1~ppa3
Candidate: 1.0-2ubuntu1~ppa3
Version table:
*** 1.0-2ubuntu1~ppa3 500
500 https://ppa.launchpadcontent.net/slyon/lp2060311/ubuntu noble/main
arm64 Packages
100 /var/lib/dpkg/status
1.0-2build1 500
500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
```
```
ubuntu@kria:~$ journalctl -u systemd-networkd-wait-online --no-pager -b
-- No entries --
```
It looks like the package you have fixes the issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Status in netplan.io source package in Noble:
Confirmed
Status in systemd source package in Noble:
Confirmed
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
