<xnox> smoser, yeah, so like cloud-init.service should want/after
systemd-resolved.service; or e.g. systemd-resolved.service should declare
itself before cloud-init.service
<xnox> smoser, i think changing it in systemd unit might be better.
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Also affects: systemd (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1734167
Title:
DNS doesn't work in no-cloud as launched by ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
