1.25.2 doesn't set up DNS information with MAAS
Bug #1528217 reported by
Cheryl Jennings
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Andrew McDermott | ||
juju-core |
Invalid
|
Critical
|
Unassigned | ||
1.25 |
Invalid
|
Critical
|
Unassigned |
Bug Description
The maas-1_
2015-12-18 20:45:27 INFO juju.api apiclient.go:270 error dialing "wss://
Containers that are started are unable to resolve any hostnames.
See later comments in bug #1525280 for more information.
See also MAAS bug #1528532 for the fact that MAAS controlled subnets return [] for dns_servers.
Changed in juju-core: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
milestone: | none → 1.25.2 |
tags: | added: blocker maas network |
tags: | added: ci |
Changed in juju-core: | |
milestone: | 1.25.2 → 2.0-alpha1 |
status: | Confirmed → Triaged |
tags: | added: regression |
Changed in juju-core: | |
status: | Triaged → Incomplete |
description: | updated |
tags: | added: kanban-cross-team |
tags: | removed: kanban-cross-team |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
assignee: | nobody → Andrew McDermott (frobware) |
Changed in juju-core: | |
status: | Incomplete → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-alpha1 → none |
milestone: | none → 2.0-alpha1 |
Changed in juju-core: | |
importance: | Undecided → Critical |
status: | New → Invalid |
To post a comment you must log in.
When address-allocation is off, 1.25.1 uses dhcp for containers. The code in apiserver/ provisioner/ provisioner. go has changed a great deal in 1.25.2 (specifically prepareOrGetCon tainerInterface s) and now renders a manual interface.
Example of /e/n/i for a container with 1.25.1:
# loopback interface
auto lo
iface lo inet loopback
# interface "eth0"
auto eth0
iface eth0 inet dhcp
With 1.25.2:
# loopback interface
auto lo
iface lo inet loopback
# interface "eth0"
auto eth0
iface eth0 inet manual
pre-up ip address add 172.16.0.5/32 dev eth0 &> /dev/null || true
up ip route replace 172.16.0.1 dev eth0
up ip route replace default via 172.16.0.1
down ip route del default via 172.16.0.1 &> /dev/null || true
down ip route del 172.16.0.1 dev eth0 &> /dev/null || true
post-down ip address del 172.16.0.5/32 dev eth0 &> /dev/null || true
Our code for getting nameservers and DNS search from resolv.conf is only triggered when address allocation is on. This change probably needs reverting (why was it made?) or we need to use resolv.conf unconditionally for containers, not just when address allocation is on.