[04:18] <mup> Bug #1738261 changed: Cannot commission machine in pod <MAAS:Expired> <https://launchpad.net/bugs/1738261>
[11:07] <mup> Bug #1621615 changed: network not configured when ipv6 netbooted into cloud-init <maas-ipv6> <verification-done> <verification-done-xenial-cloud-init> <cloud-init:Fix Released> <MAAS:Invalid> <cloud-init (Ubuntu):Fix Released> <cloud-initramfs-tools (Ubuntu):Fix Released> <cloud-init (Ubuntu
[11:07] <mup> Xenial):Fix Released> <cloud-initramfs-tools (Ubuntu Xenial):Fix Released> <cloud-init (Ubuntu Yakkety):Fix Released> <cloud-initramfs-tools (Ubuntu Yakkety):Fix Released> <https://launchpad.net/bugs/1621615>
[13:10] <sipior> howdy. i'd like to enable dynamic dns on the zone managed by maas. any way to inject a snippet into the named.conf file, like there is for dhcp?
[13:32] <morty> Hey, I have a VM running MaaS, but it is a bit buggy atm. I see that a process called "twistd3" is taking most of the cpu and ram - what is this?
[13:40] <mup> Bug #1753486 opened: maas-region-api should depend on maas-dns <MAAS:New> <https://launchpad.net/bugs/1753486>
[13:49] <utking> Hey guys!
[13:50] <utking> anyone have any clue on the twistd3 and postgres cpu usage?
[13:50] <utking> We also get deploy errors when deploying with juju, in the sense that juju waits for machines
[13:51] <utking> also i get connection lost when connecting to maas, but my mate over here morty connects just fine :S
[13:51] <kiko> utking, tell us a bit more about what your MAAS setup looks like -- single machine?
[13:51] <utking> maas is a vm running on an R710
[13:51] <utking> controlling a c6100 with 4 nodes
[13:52] <utking> dual cpu's and 48gb ram each
[13:52] <utking> it used to work, but now it doesn't
[13:52] <kiko> okay, so a separate node with a VM in it, and a blade chassis
[13:52] <utking> so i'm a bit clueless tbh
[13:52] <kiko> okay, what changed?
[13:52] <utking> yep :)
[13:52] <utking> nothing, haha
[13:52] <utking> just haven't used it for a couple of weeks
[13:52] <kiko> okay, what fails?
[13:52] <kiko> can you get to the MAAS API?
[13:53] <utking> well i for once can't connect, i can log in, and see the settings pane, but anything else gives me connection lost
[13:53] <utking> also when deploying with juju only one node gets deployed
[13:53] <kiko> you can or can't connect?
[13:53] <utking> well juju can connect
[13:54] <utking> i can't
[13:54] <kiko> how can you log in if you can't connect?
[13:55] <utking> https://gyazo.com/a501eb8464345d8f9d2e2a71291b0ec4
[13:55] <kiko> gotcha
[13:55] <kiko> you can connect, but the WS is failing
[13:55] <utking> we are a team of three people working on this, morty which is in here too
[13:56] <utking> he can connect though
[13:56] <utking> but maas still fails with the deployment
[13:56] <kiko> yep
[13:56] <utking> WS?
[13:56] <kiko> the websocket
[13:56] <utking> ah ok, how can i fix it? haha :)
[13:56] <kiko> let's look at the MAAS logs
[13:56] <kiko> any tracebacks or obvious errors?
[13:57] <utking> maas.log?
[13:59] <utking> https://pastebin.com/6VdmVSiB
[14:00] <utking> some of the nodes are a bit sleepy, so they use some time to boot. as in powers up and down for a while
[14:07] <mup> Bug #1753493 opened: [2.4a1] DHCP does not offer all DNS servers <MAAS:Triaged> <https://launchpad.net/bugs/1753493>
[14:07] <mup> Bug #1753496 opened: [2.4a1] DHCP does not offer all NTP servers <MAAS:Triaged> <https://launchpad.net/bugs/1753496>
[14:22] <utking> can't see anything that points to the errors we're having :/
[14:40] <kiko> sorry, otp so lagged
[14:47] <utking> otp? ^^
[14:50] <utking> https://gyazo.com/a473f4d4eccdd58195de8ff46133f4ef
[14:51] <utking> here you can see maas
[14:51] <utking> cpu usage i mean
[16:04] <roaksoax> q/win 4
[16:53] <mup> Bug # changed: 1665476, 1718561, 1732390, 1741302
[17:44] <kurt_> Hi guys - just looking for the information on how DNS is handled by maas.  I'm happy to RTFM, but was looking for something to actually read.  Thanks
[17:56] <chuckD> I have a question regarding MAAS with pxe boot over VLANs and was wondering if anyone had any ideas
[17:56] <chuckD> I have a JUMP server running MAAS
[17:56] <chuckD> I have 5 bare metal servers to be deployed
[17:56] <chuckD> Previously I had everything working using FLAT networks.
[17:56] <chuckD> MY PROBLEM IS:
[17:56] <chuckD> I've changed to VLANs on my networks (IPMI & brAdmin).
[17:56] <chuckD> My Servers receive VLAN Tag 141 IPMI packets from the JUMP server and act accoringly. This is expected as the serever BIOS allows for VLAN tags to be configured.
[17:56] <chuckD> Upon powerup/rest oer IPMI, My servers send unTagged (nonVLAN) BOOTP requests and I have verified that the packets make it to the IFACE of my brAdmin bridge.
[17:56] <chuckD> The packets are not passed up the the brAdmin bridge as it is on VLAN tag 148.
[17:56] <chuckD> How do I go about resolving this?
[22:34] <kurt_> maas appears to be set up correctly other than not being able to deploy.  there appears to be no internet access from the VMs to the outside world.  Any hints on what I should check?  postrouting iptables or something?
[22:36] <kurt_> and yes, I have these rules active:
[22:36] <kurt_> sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
[22:36] <kurt_> sudo iptables -A FORWARD -i eth0 -o br1 -m state \
[22:36] <kurt_>     --state RELATED,ESTABLISHED -j ACCEPT
[22:36] <kurt_> sudo iptables -A FORWARD -i br1 -o eth0 -j ACCEPT
[22:36] <kurt_> echo 'net.ipv4.ip_forward=1' | sudo tee -a /etc/sysctl.conf
[23:15] <kurt_> any help is appreciated