MAAS unmanaged network set wrong DNS information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
1.9 |
Invalid
|
High
|
Unassigned |
Bug Description
I'm trying to setup a MAAS with attached network topology. (see attached diagram.png file)
Main idea is to have a MAAS netwotk (10.10.10.0/24) with DHCP and DNS managed by MAAS to commissioning nodes, after node is successful commissioned, I setup node network like this in WebUI:
eth0 Physical fabric0 untagged 192.168.100.0/24 (DHCP)
eth1 Physical fabric0 untagged 10.10.10.0/24 (Unconfigured)
Where 192.168.100.0/24 is my LAN network where i'm going to access to node with juju or whatever.
and 10.10.10.0/24 network is only for commissioning/pxe etc
After i deploy a node with MAAS WebUI or juju bootstrap i can confirm that my local (LAN) dhcp/dns correctly configure the node
Ex:
-------
redelmann@litza:~$ ping maas-node-1
PING maas-node-1 (192.168.100.141) 56(84) bytes of data.
64 bytes from maas-node-
64 bytes from maas-node-
64 bytes from maas-node-
-------
but when i ssh to maas-node-1 and see /etc/resolv.conf this is what i see:
-------
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.100.1
nameserver 192.168.100.10
search localmaas
-------
MAAS automagic add herself as a DNS server. (See: nameserver 192.168.100.10)
Here it's not a problem because my real DNS 192.168.100.1 it's over MAAS DNS, but sometime "when i use juju bootstrap" my node resolv.conf contain:
-------
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.100.10
nameserver 192.168.100.1
search localmaas
-------
and if i ping maas-node-0 from inside node i get:
-------
ubuntu@
PING maas-node-
-------
but i should get ip from my LAN (192.168.100.0/24)
BTW: juju bootstrap fail with:
2016-02-14 19:20:08 WARNING juju.replicaset replicaset.go:98 Initiate: fetching replication status failed: cannot get replica set status: can't get local.system.
Here curtin output:
http://
and subnets output:
http://
And just in case my maas interfaces settings:
-------
ubuntu@
auto eth0
iface eth0 inet static
address 192.168.100.10
netmask 255.255.255.0
gateway 192.168.100.1
dns-nameservers 192.168.100.1
auto eth1
iface eth1 inet static
address 10.10.10.10
netmask 255.255.255.0
dns-nameservers 10.10.10.10 192.168.100.1
-------
-------
ubuntu@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.0+bzr4533-
ii maas-cli 1.9.0+bzr4533-
ii maas-cluster-
ii maas-common 1.9.0+bzr4533-
ii maas-dhcp 1.9.0+bzr4533-
ii maas-dns 1.9.0+bzr4533-
ii maas-proxy 1.9.0+bzr4533-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.0+bzr4533-
ii python-maas-client 1.9.0+bzr4533-
ii python-
-------
Changed in maas: | |
importance: | Undecided → High |
milestone: | none → 1.9.1 |
milestone: | 1.9.1 → 2.0.0 |
Changed in maas: | |
status: | New → Triaged |
no longer affects: | maas/1.10 |
We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one.