Public bug reported:
As noted in the cloud-init documentation under
https://cloudinit.readthedocs.io/en/latest/topics/network-config-
format-v2.html#networking-config-version-2 "Cloud-init does not current
support wifis type that is present in native netplan."
This is entirely understandable given the primary focus of cloud-init on
commercial clouds (which are likely entirely devoid of wifi on their
instances). However, as the Ubuntu Pi images are also cloud derived,
they use cloud-init for initial configuration, and on the Pi it's fairly
common to want a wifi-only set up.
The current state of affairs is that cloud-init is happy to copy a
"wifis" section found in network-config to the relevant netplan config
but won't apply it on the first boot. It's not a huge inconvenience to
have to reboot to get the wifi configuration applied, and this can be
worked around with hacks like running "netplan apply" in a runcmd
section. However, there is a larger problem in that it several other
cloud-init modules (in particular ssh_import_id) rely on a network
connection to operate. Hence, if a Pi user happens to have a wifi-only
set up, this effectively means they cannot use ssh_import_id sections in
cloud-init.
Is there any possibility that wifi support might be considered for a
future version?
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870346
Title:
Wifi configuration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1870346/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
