[00:50] <shahaan> Hello All, I am having a problem in (no commissioning) but deploying node whilst resolving the hostname. The reason being that maas is not setting up the dns domain-search in /etc/resolv.conf, does anybody on the channel know how to fix this ??
[00:51] <shahaan> Jan 19 06:37:15 rcstodc1r76-01 sudo[3688]:   ubuntu : unable to resolve host rcstodc1r76-01
[00:51] <shahaan> Jan 19 06:37:15 rcstodc1r76-01 sudo[3688]:   ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/systemctl status cloud-final.service
[01:22] <mpontillo> shahaan: MAAS configures cloud-init to not manage /etc/hosts, due to a bug that came up with doing so. see https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1087183
[01:23] <mpontillo> shahaan: the manage_etc_hosts flag is in /usr/lib/python3/dist-packages/maasserver/compose_preseed.py if you want to hack around with it
[01:24] <mpontillo> shahaan: that is, a default Ubuntu install solves the "unable to resolve my local hostname" issue by adding the hostname in /etc/hosts, pointing to 127.0.0.1.
[01:24] <mpontillo> shahaan: finally, I don't think MAAS supports specifying DNS search paths for deployed nodes. (lamont may know better than me, though.)
[01:37] <shahaan> Thanks mpontillo, was good help..
[01:39] <shahaan> Sorry to bother again, is there a way to specify MaaS to PXE boot only a specific whitelist of servers (either by their MAC or IP address) ??
[01:40] <mpontillo> shahaan: if you know how to configure ISC DHCP to do that, you could use DHCP snippets. (see Settings > DHCP Snippets) -- this allows you to add your own custom DHCP configuratoins
[01:42] <mpontillo> shahaan: that said, it should be relatively harmless for machines  you don't want in MAAS to PXE boot. if MAAS sees a machine PXE boot which is not in MAAS yet, it will give it a random name and add it to its database.
[01:43] <mpontillo> shahaan: MAAS will not do anything with such a machine, unless you commission it first (and possibly specify the power parameters, if the IPMI magic didn't happen).
[01:44] <mpontillo> shahaan: though I guess I can understand why you might want a whitelist, if turning on a node automatically causes it to enlist and change its IPMI settings automatically. but we want you to use MAAS on all your servers. ;-)
[01:46] <shahaan> Hey mpontillo,  we have multiple teams deploying servers (some using vDisks) though they  are on the same vlan :(, so a whitelist could have been good. But DHCP snippets is a good workaround
[01:48] <mpontillo> shahaan: I think the recommended way would be to get another VLAN so you can dedicate one to MAAS. that way you don't have clashes with more than one DHCP server running on the network (if that's the case)
[01:48] <shahaan> So for machines, setup by third party vendors (won't name them) sometimes that causes a few unnecessary conversations...
[01:49] <shahaan> Yeah, thanks for the tips mate!
[01:49] <shahaan> much appreciated
[01:49] <tdihp> mpontillo: Hi. I'm having trouble commissioning nodes
[01:50] <tdihp> mpontillo: Would you please take a look at this? https://askubuntu.com/questions/873701/maas-node-unable-to-resolve-its-own-hostname
[01:50] <tdihp> mpontillo:  Thanks very much!
[01:51] <mpontillo> tdihp: in that post, what server is `golden-moose`? is that the one you're trying to commission?
[01:53] <mpontillo> tdihp: also, just so you know, MAAS 2.1.3 is available now, so I would recommend you update to that first to fix any known issues before troubleshooting further.
[01:53] <mpontillo> https://launchpad.net/ubuntu/+source/maas/2.1.3+bzr5573-0ubuntu1~16.04.1
[01:53] <tdihp> mpontillo: Yes, the random-given name of the node.
[01:55] <tdihp> mpontillo: Ahh so it's a known issue, thanks!
[01:55] <mpontillo> tdihp: OK. are you using MAAS for your DNS? by default MAAS places machines in the .maas domain.
[01:56] <tdihp> mpontillo: Yes, I'm able to resolve the region master with .maas domain from the node.
[01:56] <mpontillo> tdihp: well, I'm not clear on the root cause of your particular problem, so I can't be certain 2.1.3 will fix the problem. but I still strongly recommend that you upgrade
[01:58] <mpontillo> tdihp: the 'connection timed out' issue is interesting though. that seems to imply that your nodes cannot communicate with the DNS server for some reason. have you ensured that your iptables rules allow DNS traffic from the nodes?
[02:00] <tdihp> mpontillo: I think so yes, I was able to dig and ping both .mass domain and external domains.
[02:01] <tdihp> mpontillo: My guess is that the storage commissioning script is timed out due to the sudo calls and other calls that would invoke hostname resolving of the node's own hostname.
[02:08] <mpontillo> shahaan: hm, interesting, it appears I was mistaken. I see "search <maas-domain>" in my /etc/resolv.conf on my commissioning node. so I would guess that, like tdihp, your issue is most likely with DNS connectivity.
[02:08] <mpontillo> tdihp: but I can't explain why you are able to ping other nodes, but not the commissioning node
[02:09] <mpontillo> tdihp: when you commission, there is an option to allow SSH and prevent the node from powering off. would you give that a try so you can troubleshoot more?
[02:13] <mpontillo> tdihp: after you SSH into the commissioning node, I would check /etc/resolv.conf on the commissioning node to ensure it's pointing to the MAAS nameserver and has your search domain in it.
[02:13] <mpontillo> tdihp: then use 'dig' to query the nameserver from the node for that hostname. dig will not consider search paths, so you'll need to add that manually
[02:15] <tdihp> mpontillo: Yes it was using the MAAS server, I've checked. However yesterday I've not seen the DNS record of the commisioning node in the MAAS http server's "DNS" list.
[02:17] <tdihp> mpontillo: But today it is. how strange. And the sudo lag went away.
[02:17] <mpontillo> tdihp: does that mean you were able to successfully commission? did you update to 2.1.3?
[02:24] <tdihp> mpontillo: I haven't upgraded yet. The /etc/resolv.conf points to the MAAS correctly. I'm able to resolve <hostname>.maas but not <hostname>
[02:25] <mpontillo> tdihp: via what mechanism? because dig will not add the search path for you, but sudo and other tools should
[02:25] <mpontillo> tdihp: for example `ping` would add the search path.
[02:25] <tdihp> mpontillo: Yes I tried ping
[02:26] <mpontillo> tdihp: ok, what was the result?
[02:27] <mpontillo> tdihp: I would also try `grep named /var/log/syslog` on the MAAS server to see if everything looks okay with the DNS server
[02:29] <tdihp> mpontillo: BTW, does MAAS add/keep DNS entry for commissioning nodes?
[02:35] <mpontillo> tdihp: okay. I would try the commissioning again then. it seems like maybe the DNS issues are no longer in your way. I replied to your askubuntu post: http://askubuntu.com/a/874005/1269
[02:36] <mpontillo> tdihp: but I've got to go now; good luck. I'll be around.
[02:37] <mpontillo> tdihp: to answer your question: commissioning - yes. when the node is finished commissioning, I believe it will clear those out.
[02:37] <mpontillo> tdihp: but while you're SSHed in, I don't think it'll remove the entries. I'm testing it now here and I see that it maintains them.
[02:38]  * mpontillo goes to eat dinner
[02:38] <tdihp> mpontillo: Thanks a lot :)
[03:45] <shahaan> Thanks mpontillo, things are looking much better now after the 2.1.3 upgrade: search erc.monash.edu.au maas
[03:46] <shahaan> That string is making a difference
[04:24] <mup> Bug #1612039 changed: MAAS Cannot Commission <MAAS:Expired> <https://launchpad.net/bugs/1612039>
[04:35] <Sandeep> Hello Guys
[04:35] <Guest2907> Anybody there?
[04:35] <Guest2907> Hello
[04:36] <mup> Bug #1612039 opened: MAAS Cannot Commission <MAAS:Expired> <https://launchpad.net/bugs/1612039>
[04:39] <mup> Bug #1612039 changed: MAAS Cannot Commission <MAAS:Expired> <https://launchpad.net/bugs/1612039>
[15:00] <YooFy> hi, hello all
[15:02] <YooFy> I search with google a great documentation for build custom image Ubuntu and windows. Do you have any links of tutorial for that
[15:02] <YooFy> ?
[15:41] <pmatulis> not to my knowledge
[22:03] <IronCom> Hi
[22:03] <IronCom> Someone here
[22:03] <IronCom> ?
[22:04] <IronCom> I would have a question to MAAS searcheing in Web but not sure about the right solution
[22:08] <pmatulis> Iron...