yahoo-eng-team team mailing list archive

[Pengpeng Sun <1880089@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Apply DatasourceOVF and pass below net config to cloud-init, DNS servers are expected to be '10.117.0.1', '10.117.0.2', DNS search domains are expected to be 'vmware.com', 'google.com'. 
 
2020-05-22 06:08:38,452 - stages.py[DEBUG]: applying net config names for {'version': 1, 'config': [{'type': 'physical', 'name': 'ens160', 'mac_address': '00:50:56:85:00:88', 'subnets': [{'control': 'auto', 'type': 'dhcp'}]}, {'type': 'nameserver', 'address': ['10.117.0.1', '10.117.0.2'], 'search': ['vmware.com', 'google.com']}]}


Here is /etc/network/interfaces.d/50-cloud-init.cfg after boot:
$ cat 50-cloud-init.cfg 
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  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
    dns-nameservers 10.117.0.1 10.117.0.2
    dns-search vmware.com google.com

auto ens160
iface ens160 inet dhcp


Ran 'systemd-resolve --status' and found DNS did NOT set as expected.
This issue only reproduces on Ubuntu Desktop but Ubuntu Server (since
it's using Netplan).

Please find attached cloud-init.logs

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Attachment added: "cloud-init.tar.gz"
   https://bugs.launchpad.net/bugs/1880089/+attachment/5375465/+files/cloud-init.tar.gz

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

Title:
  DNS set by cloud-init is not expected on Ubuntu 18.04.4 Desktop

Status in cloud-init:
  New

Bug description:
  Apply DatasourceOVF and pass below net config to cloud-init, DNS servers are expected to be '10.117.0.1', '10.117.0.2', DNS search domains are expected to be 'vmware.com', 'google.com'. 
   
  2020-05-22 06:08:38,452 - stages.py[DEBUG]: applying net config names for {'version': 1, 'config': [{'type': 'physical', 'name': 'ens160', 'mac_address': '00:50:56:85:00:88', 'subnets': [{'control': 'auto', 'type': 'dhcp'}]}, {'type': 'nameserver', 'address': ['10.117.0.1', '10.117.0.2'], 'search': ['vmware.com', 'google.com']}]}


  Here is /etc/network/interfaces.d/50-cloud-init.cfg after boot:
  $ cat 50-cloud-init.cfg 
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  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
      dns-nameservers 10.117.0.1 10.117.0.2
      dns-search vmware.com google.com

  auto ens160
  iface ens160 inet dhcp


  Ran 'systemd-resolve --status' and found DNS did NOT set as expected.
  This issue only reproduces on Ubuntu Desktop but Ubuntu Server (since
  it's using Netplan).

  Please find attached cloud-init.logs

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