[00:21] <DaToz_> any one know how to set Boot Nodes to use 9214 MTU during first boot
[00:30] <pmatulis> DaToz_, there is a VLAN setting for that
[00:38] <DaToz_> how to set the VLAN settings? don't see it in GUI
[00:41] <DaToz_> @pmatulis how to setup the MTU in VLAN settings
[01:19] <pmatulis> DaToz_, if using the web UI click the VLAN in question and fill in the field marked 'MTU'
[01:19] <pmatulis> there is an equivalent API command i'm sure
[04:23] <mup> Bug #1628189 changed: [FUJ] SSH keys: alignment in expanded table row is off <MAAS:Expired> <https://launchpad.net/bugs/1628189>
[08:34] <Duc> Hi
[08:34] <Duc> anyone can help me now ?
[08:40] <Duc> ?
[08:50] <Duc> could help to add a server to maas and deploy os for it
[08:55] <Duc> ?
[12:23] <DATAz> Guys from where i can setup the VLAN for the PXE boot
[14:28] <BlackDex> hello there, it seems the dns-forwarding isn't working
[14:28] <BlackDex> on maas 2.1
[14:31] <BlackDex> when i try to dig an external host or even a local maas controled host it doesn't resolve
[14:31] <BlackDex> even though i see the dns is running
[14:31] <BlackDex> what am i missing?
[14:38] <roaksoax> BlackDex: i'm running 2.1 and I dont have issues. YOu may want to change your DNSSEC items
[14:39] <BlackDex> i disabled that :)
[14:39] <BlackDex> no luck
[14:39] <roaksoax> BlackDex: most likely is something with your upstream DNS server
[14:40] <BlackDex> well i don't even see it's requesting anything to an upstream dns
[14:40] <BlackDex> tcpdump doesn't show that
[14:40] <BlackDex> only requests comming in
[14:40] <BlackDex> and if i request it from the maas node to the upstream dns it does work
[14:46] <BlackDex> hmm i rebooted the maas node and not it seems to be working
[14:46] <BlackDex> seems somtehing got stuck or didn't restarted correctly
[14:47] <roaksoax> BlackDex: check if bind is running
[14:47] <roaksoax> BlackDex: and check the config files
[14:47] <roaksoax> BlackDex: my guess is that your upstream dns may be blocking
[14:53] <BlackDex> roaksoax: it wasn't blocking. It is working as i could just connect to the upstream from the maas node
[14:54] <BlackDex> the reboot helped
[15:03] <roaksoax> BlackDex: strange then. I have not run into issues with it lately, but the only times i did whre due to DNSSEC config
[15:08] <BlackDex> maybe the dnssec setting didn't updated correctly
[20:02] <derekcat> Anyone an expert on image syncing problems?
[20:02] <derekcat> Racks show as "out of sync", regions say, "unknown" and the region's MAAS logs show: "Dec 12 19:55:17 maas-region-controller-01 maas.boot_image_download_service: [error] Failed to download images: Command `sudo /usr/sbin/tgt-admin --conf /var/lib/maas/boot-resources/current/maas.tgt --update ALL` returned non-zero exit status 2:#012Config file /var/lib/maas/boot-resources/current/maas.tgt not found. Exiting..."
[20:03] <derekcat> [MAAS was juju deployed]
[20:09] <derekcat> Do you have to manually create/pass that config?  Was Juju supposed to create it when it installed MAAS?
[20:09] <derekcat> Can I just make one (and if so, what needs to be in it?)
[20:10] <derekcat> And why wouldn't the boot-resources directory exist on my second region controller..?  [Also juju deployed]
[20:13] <pmatulis> derekcat, which juju charm did you use?
[20:14] <derekcat> cs:~blake-rouse/maas-region-4
[20:15] <derekcat> The command was:
[20:15] <derekcat> juju deploy cs:~blake-rouse/maas-region-4 --config maas-region-ha.yaml --to [juju machine # for an LXD ]
[20:20] <pmatulis> derekcat, afaik, that charm is not for public consumption. i don't believe it is maintained
[20:23] <rgauny> When i get to maas-enlist to the MAAS server api i get HTTP 400 BAD REQUEST.......any ideas on what this could be?
[20:23] <rgauny> i am behind a proxy but that has been set and I see that apt is getting evertything now
[20:23] <rgauny> using maas 2.0
[20:24] <rgauny> and ubuntu 16
[20:24] <derekcat> pmatuils, aw crap.  >_< Someone wrote that that was the latest verion of the charm in our local docs, not sure when that was written though..
[20:27] <rgauny> anyone?
[20:27] <rgauny> lol
[20:32] <derekcat> rgauny, ^_^" I'm not yet far enough to have those problems.. haha
[20:49] <bdx> hey whats up everyone
[20:50] <bdx> is the DHCP issue being delt with for 2.1.1+bzr5544-0ubuntu1~16.04.1 ?
[20:50] <bdx> http://paste.ubuntu.com/23620719/
[20:51] <bdx> killing off new users
[20:53] <pmatulis> derekcat, well MAAS is not hard to install. especially if you want everything on one machine
[20:56] <pmatulis> bdx, is DHCP enabled on a VLAN within MAAS?
[20:58] <bdx> pmmatulis: https://bugs.launchpad.net/maas/+bug/1649397
[20:58] <bdx> pmatulis: dhcp has to be enabled first?
[20:58] <bdx> I see
[20:59] <bdx> pmatulis: I'll close that bug then, thx
[21:04] <roaksoax> bdx: i think i beat you to it
[21:06] <pmatulis> roaksoax, did you see my maas-proxy bug?
[21:38] <bdx> roaksoax: you hit the bug too?
[21:38] <bdx> roaksoax, pmutils: I'm trying to on board a new user, na dmaas dhcp is flaking out
[21:39] <bdx> pmatutils: If the dhcp bug is a thing tell me now so I can quit (3 hrs deep into debugging)
[21:39] <bdx> of course there was alot of other cruft in the way we had to get through first
[21:40] <bdx> pmatutils, roaksoax: will you guys join https://www.freeconferencecall.com/join/obecker
[21:40] <bdx> pls
[21:43] <bdx> Teranet: https://bugs.launchpad.net/maas/+bug/1649397
[21:51] <Teranet> bug 1649397 is confimed and need's to be fixed meanwhile we need a quick work around because it's super annoying too :-)
[22:12] <derekcat> pmatulis, Indeed..  After your last message my boss and I were talking.  Trying to decide if we should go manual installed or maintain our own charm for it.
[22:12] <derekcat> Digging in more, it looks like the python script ( /usr/lib/python3/dist-packages/provisioningserver/import_images/boot_resources.py ) to make the maas.tgt is failing for some reason...
[22:14] <derekcat> pmatulis, Thank you for the help!  We'll see if we can get this started...
[22:16] <pmatulis> derekcat, lemme know if you do the manual route. it's exactly what i've been working on scripting
[22:58] <bdx> I think I understand now, MAAS only can provide DHCP to vlans inside a fabric
[22:58] <bdx> not the l2 networks themselves
[22:59] <bdx> or flat network address spaces
[22:59] <bdx> no, that doesn't seem right
[22:59] <bdx> Teranet: I think it is a bug man
[22:59] <Teranet> it is a bug
[23:00] <bdx> I'm hoping we can get some validation on that ...
[23:00] <Teranet> because even without a VLAN tag it's concidured as a VLAN = default VLAN 1
[23:00] <bdx> ok, yea
[23:01] <Teranet> funny is in MAAS the default VLAN id is 0
[23:01] <Teranet> which is not even RFC compliant LOL
[23:02] <bdx> but, I think that is just in the context of maas ... there isn't an actual network that gets tagged 0
[23:05] <Teranet> I think VLAN "0" stands for no vlan
[23:05] <bdx> yea, in the context of maas, I think it does