bionic: DNS search domains lost from cloud-init to netplan

Bug #1774540 reported by Ryan Finnie on 2018-06-01
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init
Undecided
Unassigned

Bug Description

On a deployed node with a MAAS datasource, /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg contains:

network:
  config:
  - id: enp1s0
    mac_address: 52:54:00:9a:b4:64
    mtu: 1500
    name: enp1s0
    subnets:
    - address: 10.48.7.48/21
      dns_nameservers:
      - 10.48.0.5
      gateway: 10.48.0.1
      type: static
    type: physical
  - address:
    - 10.48.0.5
    search:
    - bos01.canonistack.internal
    type: nameserver
  version: 1

But the generated /etc/netplan/50-cloud-init.yaml contains no search domains under nameservers for the interface:
# 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}
network:
    version: 2
    ethernets:
        enp1s0:
            addresses:
            - 10.48.7.48/21
            gateway4: 10.48.0.1
            match:
                macaddress: 52:54:00:9a:b4:64
            mtu: 1500
            nameservers:
                addresses:
                - 10.48.0.5
            set-name: enp1s0

Ryan Finnie (fo0bar) on 2018-06-01
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers