yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

** Bug watch added: Debian Bug tracker #783596
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783596

** Also affects: resolvconf (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783596
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1675571

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New
Status in resolvconf package in Debian:
  Unknown

Bug description:
  The change of how cloud-init renders /etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# 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

  auto eth0
  iface eth0 inet static
      address 138.197.98.102
      dns-nameservers 8.8.8.8 8.8.4.4
      gateway 138.197.96.1
      netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
      address 10.17.0.11
      netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# 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

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1675571/+subscriptions