The dyn-conf generator in the initramfs does this ## This file is generated by cloud-initramfs-dyn-netconf auto lo iface lo inet loopback manual ens3 iface ens3 inet dhcp dns-nameservers 10.0.0.2 0.0.0.0 dns-search maas
However, the resolvconf dir in /run/resolvconf does not have antything either. And while the proxy works for apt, it's clear during early boot that DNS is not working: /usr/lib/snapd/snapd[942]: snapmgr.go:411: Cannot prepare auto-refresh change: Post https://search.apps.ubuntu.com/api/v1/snaps/metadata: dial tcp: lookup search.apps.ubuntu.com on [::1]:53: as snapd pokes URLs outside the system. Reading through run dir, we have all of the settings, and it appears that resolvconf does not get updated: % cat resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN This appears to be similar to this older bug: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432829 Which relied on a systemd ifupdown helper to call resolvconf on the interface that was brought up in initramfs. I don't see that script as part of systemd anymore. Also this. https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1501033 Really feels like a regression in either the open-iscsi package, or systemd for Xenial. Ideally when this is fixed again, maas can add this as integration test to catch if this breaks again. On Mon, Aug 28, 2017 at 3:39 PM, Lee Trager <lee.tra...@canonical.com> wrote: > Attached is /run. One thing I forgot to mention. MAAS starts an > ephemeral environment by passing a user_data script to cloud-init. This > script downloads and runs all of the commissioning and testing scripts. > My understand of cloud-init is that this means cloud-init still hasn't > finished running as its running the script from MAAS. > > ** Attachment added: "run.tar.xz" > https://bugs.launchpad.net/maas/+bug/1711760/+attachment/ > 4940470/+files/run.tar.xz > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1711760 > > Title: > [2.3] resolv.conf is not set (during commissioning or testing) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711760 Title: [2.3] resolv.conf is not set (during commissioning or testing) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
