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

[Launchpad Bug Tracker]

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: resolvconf (Ubuntu Zesty)
   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 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

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

[Scott Moser]

** 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 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

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

[Scott Moser]

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: verification-done verification-donezesty

-- 
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

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

[Brian Murray]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: resolvconf (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-zesty

-- 
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

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

[Scott Moser]

** 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 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

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

[Scott Moser]

** 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 'root=http://<>/squashfs' use case.
  
  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.
  
  [Test Case]
  There are two tests for this.
  
  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
  
  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
  
  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.
  
  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).
  
  b.) this is not a container.
-   trusty uses 'running-in-container' to determine this.
-   xenial uses 'systemd-detect-virt'
+   trusty uses 'running-in-container' to determine this.
+   xenial uses 'systemd-detect-virt'
  
  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.
  
  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.
  
  [Other Info]
  
  === End SRU Template ===
  
  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 the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/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
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 

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

[Launchpad Bug Tracker]

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

  * support reading dns information written by initramfs. (LP: #1711760)

 -- Scott Moser   Wed, 08 Nov 2017 15:47:00 -0500

** Changed in: resolvconf (Ubuntu Trusty)
   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 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

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

[Scott Moser]

** 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 (to show no harm is done)"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/4998244/+files/lp-1711760-test.sh

** Attachment removed: "lp-1711760-test.sh:  works for xenial or trusty"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/5005575/+files/lp-1711760-test.sh

** Attachment removed: "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.
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

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

[Scott Moser]

** 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 verification-done-trusty

-- 
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

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

[Scott Moser]

** 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.
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

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

[Brian Murray]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed verification-failed-trusty
** Tags added: verification-needed verification-needed-trusty

-- 
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

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

[Scott Moser]

** 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.
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

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

[Scott Moser]

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 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

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

[Robie Basak]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: resolvconf (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags removed: verification-done
** Tags added: verification-needed verification-needed-trusty

-- 
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

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

[Scott Moser]

** 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 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

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

[Scott Moser]

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: "lp-1711760-test.sh:  works for xenial or trusty"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5005575/+files/lp-1711760-test.sh

-- 
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

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

[Launchpad Bug Tracker]

** 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] 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

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

[Scott Moser]

** 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: Medium => High

** 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 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
- the installation environment and also the rescue environment.
+ case of the 'root=http://<>/squashfs' use case.
+ 
+ MAAS 2.3 uses this for the installation environment and also the rescue
+ environment.  In most cases the 14.04 specific fix will only apply
+ to installation as 16.04 is most likely to be used in rescue mode.
  
  [Test Case]
  There are two tests for this.
  
  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
  
  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
  
  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.
  
  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).
  
  b.) this is not a container.
+   trusty uses 'running-in-container' to determine this.
+   xenial uses 'systemd-detect-virt'
  
  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.
  
  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.
  
  [Other Info]
  
  === End SRU Template ===
  
  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 the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT 

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

[Andres Rodriguez]

** 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 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

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

[Scott Moser]

** 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 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.
  
  [Test Case]
  There are two tests for this.
  
  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
  
  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
  
  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.
  
  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).
  
  b.) this is not a container.
  
  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.
  
  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.
  
  [Other Info]
  
  === End SRU Template ===
  
  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 the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/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
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
  
  As such, this either seems like a bug in Ubuntu, or caused by cloud-init
  when writing e/n/i.d/50-cloud-init.cfg
  
  ubuntu@manual:~$ dpkg -l | grep cloud-init
  ii  cloud-init   0.7.9-153-g16a7302f-0ubuntu1~16.04.2  

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

[Launchpad Bug Tracker]

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 (Ubuntu Xenial)
   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 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

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

[Andres Rodriguez]

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.
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

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

[Scott Moser]

** 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 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

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

[Scott Moser]

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 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

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

[Scott Moser]

> 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 the
> DNS server that was provided at the time of the first lease on boot. But
> this will only affect this impacted non-default use case. If this
> doesn't matter for you, then fine. If it does, then please mark
> verification-failed and we can go again with a fix that will cover this
> case.

Agreed.  This is not covered at this point, but never has been.
In the open-iscsi path, we've been using this code for the maas use case
since 12.04.  Your point is valid, and we're hoping in 18.04 to correctly
transition this lease over the "real root".

The answer on "What happens" right now is "Nothing".  The system will
continue to use its initramfs-provided dhcp address.  There is no
persistent process that would re-evaluate the lease.

> If not on systemd and inside a container, check will not work. We don't
> support !systemd on Ubuntu, so that should be OK. We may be on upstart
> after upgrading from Trusty; in that case the /proc/cmdline gate should
> still work so this will only affect systems booted this way using MAAS
> on Trusty and then upgraded to Xenial until next reboot.

It doesn't specifically have to use systemd as init, just have the
systemd-detect-virt.  You're right, we could have done something else
there, to cover a system that did not have that.

> Adding a udev rule that is a shell script for every network up and down.
> How does this effect udev, for example on a system with a large number
> of flapping interfaces? On a quick glance I didn't see any other shell
> script udev rule on such a wide reaching trigger.

Open-iscsi *does* have such a rule (the implementation is borrowed from
there). Also, open-iscsi is installed by default in all 16.04 images,
so while not being as ubiquitious as resolvconf, it is very common.

> Please make sure to test that the gating is working correctly in the
> non-kernel-cmdline case during SRU verification.

ACK.

-- 
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

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

[Robie Basak]

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 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 the
DNS server that was provided at the time of the first lease on boot. But
this will only affect this impacted non-default use case. If this
doesn't matter for you, then fine. If it does, then please mark
verification-failed and we can go again with a fix that will cover this
case.

If not on systemd and inside a container, check will not work. We don't
support !systemd on Ubuntu, so that should be OK. We may be on upstart
after upgrading from Trusty; in that case the /proc/cmdline gate should
still work so this will only affect systems booted this way using MAAS
on Trusty and then upgraded to Xenial until next reboot.

Adding a udev rule that is a shell script for every network up and down.
How does this effect udev, for example on a system with a large number
of flapping interfaces? On a quick glance I didn't see any other shell
script udev rule on such a wide reaching trigger.

Any race conditions before is-from-initrd gate, for example if multiple
interfaces come up close together in time? I don't see any.

Please make sure to test that the gating is working correctly in the
non-kernel-cmdline case during SRU verification.


** Changed in: resolvconf (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
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

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

[Andres Rodriguez]

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.
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

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

[Andres Rodriguez]

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 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

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

[Scott Moser]

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 resolvconf is not relevant there as resolvconf is
not used in Artful.


** No longer affects: cloud-init (Ubuntu)

** No longer affects: cloud-init (Ubuntu Xenial)

** Changed in: resolvconf (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: resolvconf (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: resolvconf (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
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

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

[Scott Moser]

** 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 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.
  
  [Test Case]
  There are two tests for this.
  
  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
  
  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
- described partially in 
-   
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
+ described partially in
+   
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
  
- 
- [Regression Potential] 
+ [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.
  
  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
- and these files have non-empty values for a variable mentioned above.
- (These files are written by the initramfs code when 'ip=' is seen).
+ and these files have non-empty values for a variable mentioned above.
+ (These files are written by the initramfs code when 'ip=' is seen).
  
  b.) this is not a container.
  
- b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
+ c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.
  
- c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
+ d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.
  
  [Other Info]
-  
+ 
  === End SRU Template ===
  
  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 the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/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
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from 

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

[Chris J Arges]

** 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.
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

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

[Andres Rodriguez]

@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 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

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

[Mark Shuttleworth]

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:
  [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

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

[Blake Rouse]

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. Exited rescue mode.
8. Ran internet connectivity test. (Passed)
9. Ran commissioning with SSH.
10. Pinged google.com. (Worked)

-- 
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

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

[MAAS Lander]

** 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 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

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

[Launchpad Bug Tracker]

** 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 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

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

[Andres Rodriguez]

** 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 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

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

[Scott Moser]

** 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"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4961827/+files/lp-1711760-test

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

-- 
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

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

[Scott Moser]

** 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 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
+ the installation environment and also the rescue environment.
+ 
+ [Test Case]
+ There are two tests for this.
+ 
+ a.) local/non-MAAS test
+ Download the test case attached.
+ Run it and follow the instructions.
+ Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
+ without the fix there would be no data in /etc/resolv.conf.  With the
+ fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
+ 
+ b.) MAAS test.
+ For the full maas test, you need to build a image stream for maas
+ with the fix included in the squashfs image and then import that
+ stream to maas and use the rescue environment and verify dns.
+ This process is beyond the scope of the SRU template, but is
+ described partially in 
+   
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
+ 
+ 
+ [Regression Potential] 
+ Regression potential should be very low.  There are gates in the code
+ to make sure that this code is inactive other than when it is explicitly
+ enabled.
+ 
+ net-interface-handler will exit without doing anything unless:
+ a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
+ and these files have non-empty values for a variable mentioned above.
+ (These files are written by the initramfs code when 'ip=' is seen).
+ 
+ b.) this is not a container.
+ 
+ b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
+ if open-iscsi has written this file due to open-iscsi root, then it
+ will handle this functionality. resolvconf will get out of the way.
+ 
+ c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
+ This lowers the scope of changes in runtime to cases with where either the
+ new flag is seen or cloud-config-url is passed. The MAAS use case will
+ contain this flag.
+ 
+ [Other Info]
+  
+ === End SRU Template ===
+ 
  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 the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/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
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
  
  As such, this either seems like a bug in Ubuntu, or caused by cloud-init
  when writing e/n/i.d/50-cloud-init.cfg
  
  ubuntu@manual:~$ dpkg -l | grep cloud-init
  ii  cloud-init   

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

[Scott Moser]

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
 
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/382

So, to build a image and stream with this content, you essentially need
to just set M2E_ADD_REPOS in the environment and then build as you
would.

example:
  export M2E_ADD_REPOS=ppa:smoser/lp1711760

-- 
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

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

[Scott Moser]

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 were put in place.  To get that to work, you have to add
an entry in /etc/hosts for 10.0.2.2 (suggest 'qemu-host').

There is a PPA available at 
  https://launchpad.net/~smoser/+archive/ubuntu/lp1711760
with the fix in place.


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

-- 
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

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

[MAAS Lander]

** 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 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

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

[Andres Rodriguez]

** 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

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

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

[Launchpad Bug Tracker]

** 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 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

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

[Andres Rodriguez]

** 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 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

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

[Scott Moser]

** 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 testing"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4961827/+files/lp-1711760-test

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/resolvconf/+git/resolvconf/+merge/331759

** No longer affects: initramfs-tools (Ubuntu)

** Also affects: resolvconf (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: resolvconf (Ubuntu)
   Status: New => In Progress

** Changed in: resolvconf (Ubuntu)
   Importance: Undecided => Medium

-- 
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

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

[Scott Moser]

** 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 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

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

[David Britton]

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
clear implementation plan.

-- 
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

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

[Andres Rodriguez]

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 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

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

[David Britton]

** 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 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

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

[Scott Moser]

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 leaves that to happen on the proxy.

-- 
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

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

[Scott Moser]

** 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 the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/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
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
  
  As such, this either seems like a bug in Ubuntu, or caused by cloud-init
  when writing e/n/i.d/50-cloud-init.cfg
  
  ubuntu@manual:~$ dpkg -l | grep cloud-init
  ii  cloud-init   0.7.9-153-g16a7302f-0ubuntu1~16.04.2 
  all  Init scripts for cloud instances
  ii  cloud-initramfs-copymods 0.27ubuntu1.4
  all  copy initramfs modules into root filesystem for later use
  ii  cloud-initramfs-dyn-netconf  0.27ubuntu1.4
  all  write a network interface file in /run for BOOTIF
  
  ubuntu@manual:~$ uname -a
  Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@manual:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  Codename:   xenial
  
- ubuntu@manual:~$ pastebinit /var/log/cloud-init.log 
+ ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
  http://paste.ubuntu.com/25342738/
- ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log 
+ ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
  http://paste.ubuntu.com/25342740/
+ 
+ Related bugs:
+  * bug 1714308: dns does not work in initramfs after configure_networking
+  * bug 1713803: replacement of resolvconf with systemd needs integration

-- 
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

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

[Scott Moser]

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 /run/network-eth0.conf with content shown in your
attached /run here.

b.) root pivots to new root (with the sqaushfs mounted loop), and keeps
/run intact.

c.) cloud-init reads the files in /run/network-eth0.conf and uses that
to override the fallback networking.  In order to avoid bouncing the
interfaces configured in initramfs, cloud-init writes 'control-manual'
stanzas in ENI rather than 'auto eth0'.  In the iscsi path, if cloud-init
wrote 'auto', then the nic might get bounced and iscsi root broken.

In the iscsi root case, its the 'net-interface-handler' that handles
transitioning the dns settings in /run/network-eth0.conf over to
the "real root".  But in this case, nothing does that.


** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

-- 
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

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

[Scott Moser]

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] 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

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

[Lee Trager]

** 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 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

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

[Ryan Harper]

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'
IPV4BROADCAST='10.0.0.255'
IPV4NETMASK='255.255.255.0'
IPV4GATEWAY='10.0.0.1'
IPV4DNS0='10.0.0.2'
IPV4DNS1='0.0.0.0'
HOSTNAME=''
DNSDOMAIN='maas'
NISDOMAIN=''
ROOTSERVER='10.0.0.2'
ROOTPATH=''
filename='pxelinux.0'
UPTIME='10'
DHCPLEASETIME='600'
DOMAINSEARCH=''


On Tue, Aug 29, 2017 at 10:19 AM, Blake Rouse 
wrote:

> 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 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

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

[Blake Rouse]

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 (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

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

[Scott Moser]

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 though.
the code that does this is at [2]

[1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/open-iscsi/tree/debian/net-interface-handler?h=applied/ubuntu/xenial-devel
[2] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/open-iscsi/tree/debian/extra/initramfs.local-top?h=applied/ubuntu/xenial-devel#n181

-- 
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

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

[Scott Moser]

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 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

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

[Ryan Harper]

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 
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

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

[Lee Trager]

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 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

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

[Ryan Harper]

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 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.


>
> ** Attachment added: "log.tar.xz"
>https://bugs.launchpad.net/maas/+bug/1711760/+attachment/
> 4938963/+files/log.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

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

[Lee Trager]

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

** Attachment added: "log.tar.xz"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4938963/+files/log.tar.xz

-- 
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

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

[Lee Trager]

** 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

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