[00:13] <mup> Bug #1660858 opened: [2.2b1, UI] Cannot add a snippet via the UI <MAAS:Triaged> <https://launchpad.net/bugs/1660858>
[00:13] <mup> Bug #1660859 opened: [2.2b1, UI] No error surface when adding a snippet <error-surface> <MAAS:Triaged> <https://launchpad.net/bugs/1660859>
[00:16] <mup> Bug #1660860 opened: Deploying Ubuntu 14.04 LTS <MAAS:New> <https://launchpad.net/bugs/1660860>
[00:43] <mup> Bug #1660863 opened: [2.2b1, UI] Can't select a node when adding a DHCP snippet node <MAAS:Triaged> <https://launchpad.net/bugs/1660863>
[00:43] <mup> Bug #1660864 opened: [2.2b1, UI] Cannot add a package repository via the UI <MAAS:New> <https://launchpad.net/bugs/1660864>
[01:04] <mup> Bug #1660866 opened: [2.2b1, UI] No error surface when adding a Package Repository <error-surface> <MAAS:Triaged> <https://launchpad.net/bugs/1660866>
[03:57] <g3> roaksoak. So I wiped MAAS and started over.... now it works
[04:26] <mup> Bug #1660883 opened: Node failed to deploy, says to check installation log, but there isn't one <cdo-qa-blocker> <oil> <MAAS:New> <https://launchpad.net/bugs/1660883>
[08:12] <jlec_> morning
[08:13] <jlec_> Is Maas and/or Canonical @ FOSDEM this weekend?
[08:13] <jlec_> I repacked an ubuntu squashfs because I like to have python in the base image. How would I add it as a custom image?
[15:44] <Sjlver> Hi,
[15:46] <Sjlver> I'd like to ask for some helps with nodes that are stuck in commissioning. The nodes boot from PXE, request the commissioning image, and then boot that image and show an Ubuntu login prompt. After the prompt, nothing happens until commissioning times out after 20 minutes.
[15:46] <Sjlver> I've already checked the system time; it is precise
[15:47] <Sjlver> It also doesn't seem to be a network issue. If I boot the node in rescue mode, I can SSH into it from the master, and vice versa.
[15:47] <Sjlver> Any more ideas how to debug this?
[15:54] <mup> Bug #1661022 opened: [2.2beta1] artifact collection fails because of MAAS 2.2 API errors - TypeError: Incorrect padding <cdo-qa-blocker> <oil> <MAAS:New> <https://launchpad.net/bugs/1661022>
[16:35] <capncrunch4me_> we have been trying for 4 days to get MAAS to properly deploy a server
[16:36] <capncrunch4me_> maas will work properly up and until it needs to deploy a node
[16:36] <capncrunch4me_> then it will hang on installing
[16:36] <capncrunch4me_> and say that the metadata is missing
[16:36] <capncrunch4me_> this is a fresh maas build running stable
[16:39] <pmatulis> capncrunch4me_, what actual version is it?
[16:39] <capncrunch4me_> latest
[16:40] <capncrunch4me_> i just did a stable load onto 16.04
[16:40] <capncrunch4me_> 2.1.3+bzr5573
[16:40] <capncrunch4me_> should I try with the “next” package?
[16:45] <mup> Bug #1661037 changed: Cannot deploy Ubuntu 16.04 nodes <MAAS:New> <https://launchpad.net/bugs/1661037>
[16:45] <capncrunch4me_> that is my bug
[16:54] <mup> Bug #1661037 opened: Cannot deploy Ubuntu 16.04 nodes <MAAS:New> <https://launchpad.net/bugs/1661037>
[17:00] <mup> Bug #1661037 changed: Cannot deploy Ubuntu 16.04 nodes <MAAS:New> <https://launchpad.net/bugs/1661037>
[17:01] <pmatulis> capncrunch4me_, so you hit an already-reported bug
[17:02] <capncrunch4me_> lucky me
[17:03] <pmatulis> capncrunch4me_, consider adding your info
[17:03] <capncrunch4me_> :) I opened the original one. For some reason I didnt think they were related
[17:03] <pmatulis> ohh
[17:04] <pmatulis> well, there is info missing. are you going to include it?
[17:04] <capncrunch4me_> yes, I will update ticket
[17:04] <pmatulis> ty
[17:08] <capncrunch4me_> goint to try this in an lxd container to make iterations faster
[17:09] <capncrunch4me_> should I try with “next"
[18:16] <Sjlver> I might have found a reason for my commissioning problem. The following shows up in /var/log/maas/maas.log every 5 minutes:
[18:16] <Sjlver> [warn] I/O error while syncing boot images. If this problem persists, verify network connectivity and disk usage.
[18:16] <Sjlver> [warn] Finished importing boot images, the region does not have any boot images available.
[18:16] <Sjlver> Any ideas how to debug/fix this?
[18:49] <Sjlver> OK, problem solved. The solution is pretty interesting, so let me post it here for reference. A while ago, I configured the MAAS master to use https, and changed the maas_url in the configuration accordingly. In addition, I generated a valid SSL certificate, and changed /etc/apache2/conf-enabled/maas-http.conf to point to that certificate. So far so good, things worked.
[18:50] <Sjlver> Now some MAAS update apparently, silently, overwrote /etc/apache2/conf-enabled/maas-http.conf and caused it to revert to the self-signed certificate.
[18:50] <Sjlver> This causes nodes to silently fail to enlist or commission :(
[19:12] <capncrunch4me_> pmatulis: updated ticket, the lastest version of MAAS is basically broken. You cant deploy a node
[19:12] <capncrunch4me_> it will report and commission fine, just cant deploy
[19:13] <capncrunch4me_> again, this is plain jane deployment of maas
[20:19] <g3_> Anyone around?
[21:20] <jwitko> Hey guys, under the list of supported operating systems Debian is not included.  Is this just because it should be obvious?  or does MAAS not support booting debian?
[21:25] <roaksoax> jwitko: we haven't done to deploy debian
[21:25] <roaksoax> don't work*
[21:25] <roaksoax> but we could definitely support it
[21:26] <g3_> roaksoax, SO I wiped / purged maas from the system and started over.
[21:26] <g3_> it all works now
[21:26] <g3_> Not sure what happened, but hopefully those logs in the ticket can help some?
[21:27] <roaksoax> g3_: we will look into that
[21:27] <roaksoax> g3_: thanks for putting them there
[21:27] <roaksoax> g3_: tstrange insdeed but at least we can logs
[21:28] <g3_> Is there an easy way to tag through the cli?
[21:28] <g3_> maas admin node NODENAME tag=?
[21:30] <g3> maas $PROFILE tag update-nodes $TAG_NAME add=$SYSTEM_ID
[22:32] <g3> roaksoax I'm almost there! I have a slight interface/route/gateway issue
[22:32] <g3> Any chance you're there and can chat for 5 minutes?
[22:47] <g3> Two subnets S1 and S2. S1 is OOB management. S2 is open to the world.
[22:47] <g3> if I just have S1 set in the interfaces, it works as expected, but can't talk to the internet
[22:47] <g3> If I have S1 and S2 set, same thing.
[22:48] <g3> If I change the default gateway to S2 (maas admin itnerfaces set-default-gateway sysid interfaceid) it then can't deploy as it can not connect to the maas server to pull cloud-init bits.
[22:49] <g3> I think I need the default gateway set to S1, but a static route from S1 to S2's gateway with a metric?