On Fri, Aug 25, 2017 at 5:47 PM, Lee Trager <email address hidden>
wrote:
> This is easily reproducible by booting into any MAAS ephemeral
> environment(commissioning, testing, rescue mode). Apt works regardless
> of /etc/resolv.conf being set as apt is configured to proxy through the
> rack controller. MAAS is giving the DNS server over DHCP as running
> dhclient sets /etc/resolv.conf.
>
> I've attached the files you requested, there is nothing in /var/lib/dhcp
>
Can you tar up /run ? The initramfs is doing the initial network
configuration.
On Fri, Aug 25, 2017 at 5:47 PM, Lee Trager <email address hidden>
wrote:
> This is easily reproducible by booting into any MAAS ephemeral commissioning, testing, rescue mode). Apt works regardless
> environment(
> of /etc/resolv.conf being set as apt is configured to proxy through the
> rack controller. MAAS is giving the DNS server over DHCP as running
> dhclient sets /etc/resolv.conf.
>
> I've attached the files you requested, there is nothing in /var/lib/dhcp
>
Can you tar up /run ? The initramfs is doing the initial network
configuration.
> /bugs.launchpad .net/maas/ +bug/1711760/ +attachment/ +files/ log.tar. xz /bugs.launchpad .net/bugs/ 1711760 /bugs.launchpad .net/maas/ +bug/1711760/ +subscriptions
> ** Attachment added: "log.tar.xz"
> https:/
> 4938963/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [2.3] resolv.conf is not set (during commissioning or testing)
>
> To manage notifications about this bug go to:
> https:/
>