Curtin no longer sets search domain in curtin config

[adolfo94]

Hi everyone,

I had some time that I don’t deploy a machine with maas.
When I try to deploy a new machine, my workflow has broken due the DNS search key in curting network config is missing:

/etc/cloud/cloud.cfg.d/50-curtin-networking.cfg :

network:
  ethernets:
    ens33:
      addresses:
      - 172.16.0.10/24
      gateway4: 172.16.0.1
      match:
        macaddress: 00:00:00:00:00:00
      mtu: 1500
      nameservers:
        addresses:
        - 172.16.1.2
        - 172.16.1.3
      set-name: ens33
  version: 2

I have checked a older machine and the search is configured:

network:
  bonds:
    bond0:
      addresses:
      - 172.16.0.20/24
      gateway4: 172.16.0.1
      interfaces:
      - ens14f0np0
      - ens1f0np0
      macaddress: 00:00:00:00:00
      mtu: 1500
      nameservers:
        addresses:
        - 172.16.0.2
        - 172.16.0.3
        search:
        - mydomain.local  <---- this is missing
      parameters:
        down-delay: 0
        mii-monitor-interval: 100
        mode: balance-rr
        transmit-hash-policy: layer2
        up-delay: 0
  version: 2

Is this a desired change?

[r00ta]

Hi there,

Do you have allow_dns on that subnet?

[adolfo94]

Hi @r00ta ,
It’s unchecked, I have checked again and launched a new deploy.
I will keep you informed.

[adolfo94]

It was not necessary to finish deploying the machine, I see that maas itself already returns the search field in the curtin.

Adds the search, but adds itself to the DNS list:

$ maas token machine get-curtin-config tcyrkk | yq '.network'
ethernets:
  ens33:
    addresses:
      - 172.16.0.10/24
    gateway4: 172.16.0.1
    match:
      macaddress: 00:00:00:00:00:00
    mtu: 1500
    nameservers:
      addresses:
        - 172.16.0.10  <---- My maas ip
        - 172.16.0.2
        - 172.16.0.3
      search:
        - mydomain.local
    set-name: ens33
version: 2

[r00ta]

Nice, glad it worked!