This problem is somehow created only on the first boot, most likely by
some magic being performed by cloud-init. If the created instance is
rebooted, there is no problem and systemd-networkd can be restarted with
no problems.
Marking this as invalid for system as this isn't a systemd issue, this
is a cloud problem, probably with cloud-init, or maybe with the cloud
image.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902960
Title:
Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
resolution in some cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1902960/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
