[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

This bug was fixed in the package resolvconf - 1.79ubuntu4.1 --- resolvconf (1.79ubuntu4.1) zesty-proposed; urgency=medium * support reading dns information written by initramfs. (LP: #1711760) -- Scott Moser Fri, 08 Dec 2017 14:47:54 -0500 ** Changed in:

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Tags removed: verification-donezesty ** Tags added: verification-done-zesty ** Tags removed: verification-done -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I've verified zesty with the script that is attached. Output is shown here. ** Attachment added: "verification log of zesty" https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5023065/+files/zesty.log ** Tags removed: verification-needed verification-needed-zesty ** Tags added:

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Hello Andres, or anyone else affected, Accepted resolvconf into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu4.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Also affects: resolvconf (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: resolvconf (Ubuntu Zesty) Status: New => Triaged ** Changed in: resolvconf (Ubuntu Zesty) Importance: Undecided => Medium -- You received this bug notification because you are a

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Description changed: === Begin SRU Template === [Impact] Without this fix applied, dns settings provided to the dhcp response in the initramfs are not reflected in the "real root". Thus dns resolution does not work. Of most interest was the MAAS use case of the

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

This bug was fixed in the package resolvconf - 1.69ubuntu1.3 --- resolvconf (1.69ubuntu1.3) trusty-proposed; urgency=medium * Fix bad shell syntax in newly added /lib/resolvconf/net-interface-handler (LP: #1711760) resolvconf (1.69ubuntu1.2) trusty-proposed; urgency=medium

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Attachment removed: "lp-1711760-test.sh: script to aid in testing default to proposed" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh ** Attachment removed: "updated recreate script that supports running in 'control' mode

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Attachment added: "output of running script with comments showing fix." https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5006686/+files/verify-trusty-lp-1711760.txt ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Attachment added: "final version of recreate script" https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5006685/+files/lp-1711760-test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Hello Andres, or anyone else affected, Accepted resolvconf into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resolvconf/1.69ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Attachment added: "one more try at reproduce script." https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/5006069/+files/lp-1711760-test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

testing showed that I uploaded a bad version. Fixed in a new upload https://launchpadlibrarian.net/345007871/resolvconf_1.69ubuntu1.3_source.changes ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-failed verification-failed-trusty -- You received this

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Hello Andres, or anyone else affected, Accepted resolvconf into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resolvconf/1.69ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: resolvconf (Ubuntu Trusty) Status: Confirmed => In Progress ** Changed in: resolvconf (Ubuntu Trusty) Assignee: (unassigned) => Scott Moser (smoser) ** Changed in: resolvconf (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I've uploaded the same change that is in xenial but slightly adjusted for trusty. I'm attaching an updated recreate script that works for both xenial and trusty. (trusty needs to install the cloud-initramfs-dyn-netconf package to mimic the MAAS ephemeral environment). ** Attachment added:

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Merge proposal linked: https://code.launchpad.net/~smoser/ubuntu/+source/resolvconf/+git/resolvconf/+merge/37 -- 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]

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Also affects: resolvconf (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: resolvconf (Ubuntu Trusty) Status: New => Confirmed ** Changed in: resolvconf (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: resolvconf (Ubuntu Trusty) Importance:

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Status: Fix Committed => Fix Released -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Description changed: === Begin SRU Template === [Impact] Without this fix applied, dns settings provided to the dhcp response in the initramfs are not reflected in the "real root". Thus dns resolution does not work. Of most interest was the MAAS use case of the

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

This bug was fixed in the package resolvconf - 1.78ubuntu5 --- resolvconf (1.78ubuntu5) xenial; urgency=medium * support reading dns information written by initramfs. (LP: #1711760) -- Scott Moser Mon, 23 Oct 2017 12:44:53 -0400 ** Changed in: resolvconf

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I've verified these two manually! Thanks for all the work! ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Attachment added: "updated recreate script that supports running in 'control' mode (to show no harm is done)" https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4998244/+files/lp-1711760-test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

the attached log shows this is working when expected and not when not expected. ** Attachment added: "my.log: log of running lp-1711760-test.sh" https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4998243/+files/my.log -- You received this bug notification because you are a member of

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

> I have reviewed this. +1 from ~ubuntu-sru. Thanks for the thoughtful review. > What happens when the DHCP lease acquired in the initramfs expires? What > if the DNS server changes after a new lease? Really it's the entire DHCP > lease that needs handing over from the initramfs rather than just

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I have reviewed this. +1 from ~ubuntu-sru. Regression risk is mitigated as Scott says by careful gating of the active code to limit exposure of these changes to the non-default use case only. I did note the following: What happens when the DHCP lease acquired in the initramfs expires? What if

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Bumping this to critical provided that at this point, this completely breaks MAAS. ** Changed in: resolvconf (Ubuntu Xenial) Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Also, I've tested this in GMAAS and confirm the fix works! -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I updated some state on the tasks. As justification, this fix is in resolvconf, so I dropped cloud-init. I had added it thinking it might need integration, but it did not. Also marked the 'ubuntu' task as "won't fix". The problem did not currently exist in Artful, and the solution provided in

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Description changed: === Begin SRU Template === - [Impact] + [Impact] Without this fix applied, dns settings provided to the dhcp response in the initramfs are not reflected in the "real root". Thus dns resolution does not work. Of most interest was the MAAS use case of the

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Also affects: resolvconf (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

@Mark, I do have access (just tested). I'll give it a try tomorrow! Thanks! -- 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

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I think Andres has access to the GMAAS, would appreciate if he could verify the fix there. If not, let me know and I can try it. Thanks! -- 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:

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I have verified that smoser changes do work with MAAS. Testing steps: 1. Generated xenial amd64 image stream using smosers PPA. 2. Installed MAAS. 3. Removed the workaround in MAAS. 4. Imported the xenial amd64 image with smosers PPA. 5. Entered rescue mode. 6. Pinged google.com. (Worked) 7.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Status: Fix Released => Fix Committed -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Merge proposal linked: https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/332330 -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Status: Fix Committed => Fix Released -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Attachment added: "lp-1711760-test.sh: script to aid in testing default to proposed" https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh ** Attachment removed: "lp-1711760 script to aid in testing"

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Description changed: + === Begin SRU Template === + [Impact] + Without this fix applied, dns settings provided to the dhcp response + in the initramfs are not reflected in the "real root". + + Thus dns resolution does not work. Of most interest was the MAAS use + case of the

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

I've also asked the MAAS team to build a maas-images with an updated squashfs. I made a couple changes to lp:maas-images on Friday to make that easy to do http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/381

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

This script runs and demonstrates functional dns. It launches a guest with a custom kernel command line pointing to a nocloud datasource running on the host. It uses user mode networking to seed a dns server and a dns search. The 'seedfrom' is done over dns which would not work if this change

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Status: In Progress => Fix Committed -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Assignee: (unassigned) => Andres Rodriguez (andreserl) ** Changed in: maas Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711760

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Merge proposal linked: https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/331968 -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Milestone: 2.3.0 => 2.3.0beta2 -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) ** Attachment added: "lp-1711760 script to aid in

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Hi Andres -- This fix is complicated in that the networking involved with passing rooturl= and ip= gets into hairy bits in the distro and the handover from initramfs to the rootfs, not just cloud-init. It still needs to be discussed. We'll make sure we put an update on here once we have a more

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Hi All, So what's the latest status on this and/or what is the proposed fix? -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: cloud-init (Ubuntu) Importance: Medium => High -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Just for future reference, it was unclear in my mind why the logs showed apt-get update succeeding which seemed to require dns (archive.ubuntu.com). The reason that worked was that http_proxy was set for apt. When using an http proxy, the client system does not resolve the Host, but rather

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Description changed: Using MAAS 2.3, during commissioning (and likely in the rest of the ephemeral environment) we have noticed that resolv.conf is not set with the DNS server. That said, during the commissioning process, MAAS does not send any metadata to cloud-init to configure

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Blake. that makes sense. I had forgotten about that switch to using rooturl. So here is what happens. I do not think this is regression, though. I'm not sure how it could have ever worked. a.) initramfs (rooturl) configures networking due to 'ip=' on the command line. this process writes files

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

marked this 'confirmed' since I am pretty sure I understand the error. I'm not necessarily sure on the right way to fix it. -- 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]

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Status: New => Confirmed -- 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

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Possibly not then, the device that was in use has a net-.conf file; If we don't have iscsi then what other script is going to create the .interface file? Here's the conf file for ens3 (the device in use) % cat run/net-ens3.conf DEVICE='ens3' PROTO='dhcp' IPV4ADDR='10.0.0.54'

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Scott, Since we are no longer using iscsi and using the squashfs over HTTP, would open-iscsi even be used? -- 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Your /run does not have a /run/initramfs/open-iscsi.interface file that file should have been written by the initramfs local-top code. if it is not present, then resolvconf will not be run by net-interface-handler [1] and /etc/resolv.conf not updated. I'm not sure how that could have happened

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Ryan, fwiw, I wrote at https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1713537/comments/1 a description of how all this is tied together in xenial->zesty. the ifupdown helper is still present, it has just moved. -- You received this bug notification because you are a member of

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

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

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

On Fri, Aug 25, 2017 at 5:47 PM, Lee Trager 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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

** Summary changed: - [2.3] resolv.conf is not set (during commissioning) + [2.3] resolv.conf is not set (during commissioning or testing) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711760