1.9 doesn't set the dns-search option in the generate /etc/network/interfaces

Bug #1496562 reported by Blake Rouse on 2015-09-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Blake Rouse
curtin
High
Unassigned

Bug Description

When a node is deployed in MAAS 1.9 and curtin generates the /etc/network/interfaces it does not include the dns-search path. So anytime a user does:

sudo they see:
sudo: unable to resolve host maas1

To fix this issue both MAAS and curtin need to be fixed.

1. MAAS needs to provide a list of dns-search paths for curtin.
2. Curtin needs to place that information in the generated /etc/network/interfaces.

Related branches

Changed in curtin:
status: New → Triaged
importance: Undecided → High
Ryan Harper (raharper) wrote :

Attached branch has a fix. dns-search can be appended in two places:

- subnets
  - type static
    address 1.1.1.1
    dns-search:
       - path1
       - path2

or

- subnets
  - type static
    address 1.1.1.1
    dns-search: path1 path2

or

- nameserver
  address: 8.8.8.8
  search: path1 path2

or

- nameserver
  address: 8.8.8.8
  search:
    - path1
    - path2

curtin will inject

dns-search <paths> either under the specified interface (if configured under subnets)
or if using nameserver config, then it will appear underneath all iface lines.

Ryan Harper (raharper) wrote :

Fix has landed in trunk.

Changed in curtin:
status: Triaged → Fix Committed
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers