[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf

[Jeff Lane]

Maybe I misunderstand the "region controller" concept or my
understanding of the MAAS ecosystem is outdated.

AIUI there is a "region controller" that communicates with multiple
"cluster controllers" that further manage multiple "nodes":


              /-- cluster foo -> node1.foo, node2.foo, node3.foo ... nodeX.foo
            /
region -- cluster bar -> node1.bar, node2.bar, node3.bar ... nodeX.bar
           \
            \-- cluster baz -> node1.baz, node2.baz, node3.baz, ... nodeX.baz

Is that incorrect?  That's what I meant when I said "region controller"
my point was just in agreement that "whatever entity" controls DNS for
the MAAS environment should be aware and able to resolve it's own DNS
within the MAAS environment.

Part of my confusion is that I lack the hardware to do a config where I
install maas-region-controller on one machine and maas-cluster-
controller on another and then add nodes to see where things fall.  It's
a very complex system and there are gaps in my view of how it all plays
together.


Additionally this DID create an issue with juju as I did a juju bootstrap on my only maas server to bootstrap my only node.  Node booted and deployed and bootstrapped BUT when I attempted a 'juju ssh 0' to ssh to the bootstrap node, that failed because juju was trying to access the FQDN of node0, NOT it's IP address.

So even though MAAS set the FQDN of the node (supermicro.master in this
case) the inability to resolve those names inside the MAAS environment
caused juju to be unable to contact those nodes/units.  This was easily
resolved by editing /etc/resolv.conf on my MAAS server (it contains
everything, maas-region-controller, maas-cluster-controller and ALL
dependencies and ancillary packages/services AND all the juju stuff as
well) and making sure my MAAS server could use it's own instance of bind
for DNS resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1274527

Title:
  MAAS doesn't put its DNS server in resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1274527/+subscriptions