yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1745352@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

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

Title:
  Nameservers only in lo interface resulting in empty /etc/resolv.conf

Status in cloud-init:
  Expired

Bug description:
  Using OpenStack with ubuntu 16.04 and cloud-init
  v17.1-46-g7acc9e68-0ubuntu1~16.04.1 and a network configuration
  similar to this:

  {
      "services": [
          {
              "type": "dns",
              "address": "192.84.150.104"
          }
      ],
      "networks": [
          {
              "network_id": "some-id",
              "type": "ipv4",
              "netmask": "255.255.254.0",
              "link": "tapd2ae68bb-fa",
              "routes": [
                  {
                      "netmask": "0.0.0.0",
                      "network": "0.0.0.0",
                      "gateway": "212.189.144.1"
                  }
              ],
              "ip_address": "212.189.145.68",
              "id": "network0"
          }
      ],
      "links": [
          {
              "ethernet_mac_address": "some:mac",
              "mtu": 1500,
              "type": "bridge",
              "id": "tapd2ae68bb-fa",
              "vif_id": "d2ae68bb-fa58-4de6-966d-504185571913"
          }
      ]
  }

  The DNS is configured only in lo interface in
  /etc/network/interfaces.d/50-cloud-init.cfg:

  auto lo
  iface lo inet loopback
      dns-nameservers 192.84.150.104

  Resulting in an empty /etc/resolv.conf

  Should the name servers be configured in the other interface?

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