Public bug reported:
I have a SpacemiT K3 picoITX system with 2 Ethernet ports and a wireless
card.
systemd-networkd.service assigns addresses to enP2p1s0 and to end0 but not to
the WiFi card wlP4p1s0.
This is expected as this is a first boot of our preinstalled 26.10 image.
cloud-init-network.service/start never finishes.
My expectation is:
cloud-init-network.service/start should time out.
neplan should consider wireless connections always as optional.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Milestone: None => ubuntu-26.10
** Changed in: cloud-init (Ubuntu)
Milestone: None => ubuntu-26.10
** Summary changed:
- cloud-init-network.service fails to start
+ cloud-init-network.service fails to start in reasonable time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169857
Title:
cloud-init-network.service fails to start in reasonable time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2169857/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
