@Scott, Sure, we can all improve but I just want to note one thing. The "Silly" config that MAAS sends to curtin is valid config. That yields valid configuration in Xenial. Since Curtin is now passing the /same/ configuration to cloud-init, cloud-init is not generating valid configuration in Bionic. Despite the fact that theres a "global" DNS, there's also DNS defined for the bridge, but cloud-init is not writing the bridge config correctly.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
