[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
So this bit us again when trying to deploy LDS. The process there is: Install/configure MAAs Populate MAAS on MAAS, install juju Juju bootstrap juju-deployer install LDS then go to LDS and it does more stuff. In this case it really caused pain in several cases where juju would say bootstrap failed (because it was unable to resolve a node name, since juju bootstrap checks the node hostname rather than the node IP) even though bootstrap was successful. I'm sure we probably retried bootstrap at least 2 - 3 times thinking it had failed when in reality all that had happened was DNS issues causing the health check to fail. Also, when trying to deploy stuff to 74 nodes, not being able to access the node via hostname from the maas server REALLY SUCKED. It is a pain to have to click through system pages to find an IP address because you're unable to ssh node-host-name.maas from MAAS. It's not a trivial solution, Julian points that out well, but it IS one that makes debugging and sometimes deployments more painful than they should be, especially when you're using more than a handful of nodes. That said, I understand that MAAS is designed to be run distributed across several bits at scale, but we're taking about DNS. Perhaps DNS should be controlled at the region controller level then (If it's not already, I confess that I don't know where in the stack bind sits in relation to region-controller, cluster-controller, haproxy, PostgreSQL and so forth), with each cluster controller updating the region DNS data, and every cluster passing the region controller as the DNS server to all nodes as well as using the region controller as the cluster's primary DNS. Or at least something like that. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Your case is but one possible configuration of a MAAS installation, where you have the whole region on a single box. The region is a collection of application server threads, PostgreSQL and the soon-to-be-removed Celery. All of these components can be running across varied hosts for HA reasons. MAAS was not designed to have a region on a single machine. In your case, the convenience package called maas which installs everything on a single host could set resolv.conf, for convenience, since you are also using the same host as the juju client. But in the case of you using a totally separate host for MAAS access, this won't help and MAAS cannot help you at all. I hope that makes it clearer! -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Additionally, do we not also use juju, region and cluster on the same NUC inside the Orange Box? So it seems like it would be important from the OB perspective to fix this as well. Just an additional use case. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Hrmmm... it just bit me while trying to test out the checkbox charm on bare metal from my private maas server. and it's not just a matter of juju. for example, MAAS is successfully updating the zone files: npdxh IN CNAME 10-0-0-123 and I can't ssh to my node by hostname: ubuntu@critical-maas:/etc/bind/maas$ ssh npdxh ssh: Could not resolve hostname npdxh: Name or service not known so I have to know the IP address. The NODE, does at least resolve DNS on the MAAS network properly: ubuntu@npdxh:~$ host npdxh npdxh.master is an alias for 10-0-0-123.master. 10-0-0-123.master has address 10.0.0.123 And I'm sure we all already know that much. IN any case, this is an annoyance, it's fixable, but really, the MAAS region controller (and cluster in this case since they're all one system for me) should be able to resolve its own DNS entries. From a more important use case, for certification purposes, if I am going to get testers to use juju and the checkbox charms for testing, I can not also require them to provide separate systems to serve as region or cluster or juju systems just for DNS resolution to work. Nor does it look good to tell engineers at partner sites to manually work around this. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Bear in mind that there is no region controller as a single entity, it is comprised of many discrete components. So far people have been installing them all in the same place using the convenience of the maas meta package, so if installing that package it could update resolv.conf as well, but in other cases it's not a simple case of doing that. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
So we have discussed this before and the reason why this hasn't been addressed is: 1. resolv.conf gets updated automatically by network manager in some cases, hence this will cause the change to be lost. 2. This is only required when juju is being used from the MAAS region controller, meaning that the client should configure it's resolv.conf when pointing to a MAAS server. Does this make any sense? ** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) ** Changed in: maas (Ubuntu) Status: New = Confirmed ** Changed in: maas (Ubuntu) Importance: Undecided = Low -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
