[00:58] <roaksoax> .
[10:50] <mup> Bug #1713695 opened: QueryDict error when creating an iprange via the API <MAAS:New> <https://launchpad.net/bugs/1713695>
[10:53] <mup> Bug #1713695 changed: QueryDict error when creating an iprange via the API <MAAS:New> <https://launchpad.net/bugs/1713695>
[10:59] <mup> Bug #1713695 opened: QueryDict error when creating an iprange via the API <MAAS:New> <https://launchpad.net/bugs/1713695>
[14:59] <zdw> Anyone having trouble with MaaS 1.9.5 not downloading a working copy of Ubuntu 14.04 ?
[14:59] <zdw> On new installs, I end up with a ton of snapshot directories in /var/lib/maas/boot-resources: https://gist.github.com/zdw/064fa5c2eea2dbfb3747fd6fdcd8bd23
[15:00] <zdw> Compared to a working system, where there is one of these, and a `current` that symlinks to it, which doesn't seem to be happening.
[15:23] <roaksoax> zdw: do you have any logs ? the clusterd.log should shed more light
[15:24] <roaksoax> zdw: maas 1.9 has not changed at all, so if there's a problem, the problem is with the image publication
[15:26] <zdw> clusterd.log: https://gist.github.com/zdw/e9840346da93fbf5e9a5d7db1ed008b9
[15:27] <zdw> Looks like the `usr/lib/shim/shim.efi.signed` can't be found in something that was downloaded?
[15:30] <roaksoax> zdw: could be that a recent update of grub has removed such file
[15:32] <roaksoax> zdw: have ytou upgraded your machine recently ? what packages have been upgraded?
[15:33] <zdw> This is a fresh install, as of yesterday.  Installs from previous days worked fine.
[15:35] <zdw> I'm thinking you're right about the image publication being the issue.
[15:36] <zdw> Who publishes those images?
[15:36] <roaksoax> zdw: https://launchpad.net/ubuntu/+source/shim-signed/1.32~14.04.2
[15:36] <roaksoax> zdw: it is not the issue
[15:36] <roaksoax> zdw: the issue is that update I think
[15:40] <roaksoax> zdw: replied to your ML email for record
[15:41] <roaksoax> zdw: but just copy shimx64.efi.signed to shim.efi.signed in /var/lib/shim/
[15:49] <zdw> Still getting this error in clusterd.log: `exceptions.IOError: [Errno 2] No such file or directory: u'/tmp/maas-xRIMS6/usr/lib/shim/shim.efi.signed'`
[15:50] <zdw> My process: https://gist.github.com/zdw/ab4f730011550ac72c97c623a17bd70d
[16:01] <zdw> Looks like the path might need to be `/usr/lib/shim` not `/var/lib/shim` ?
[16:09] <zdw> Tried with `/usr/lib/shim/shim.efi.signed` and still no joy.
[16:10] <zdw> Is the `/tmp/maas-xxxx` a tempdir that is downloaded/decompressed to?
[16:16] <roaksoax> i need to look into that
[16:16] <roaksoax> i dont have a 1.9 in hand since that's pretty old now
[16:53] <mup> Bug #1713771 opened: [2.2, CLI] "vlans create" should allow space assignment (as "vlan update") <4010> <MAAS:New> <https://launchpad.net/bugs/1713771>
[17:16] <arunkumar413_> can i run wordpress blogging system on maas
[17:53] <pmatulis> aru...
[18:14] <mup> Bug #1713788 opened: [2.x] When adding a custom image filetype needs to be overwriten when it could be determined <MAAS:Triaged> <https://launchpad.net/bugs/1713788>
[18:44] <roaksoax> zdw: i have a patch if you wanna try it
[18:44] <mup> Bug #1713795 opened: [1.9] Unable to install 14.04, shim.efi.signed renamed <MAAS:Triaged> <maas (Ubuntu):Triaged by andreserl> <https://launchpad.net/bugs/1713795>
[18:45] <mup> Bug #1713795 opened: [1.9] Unable to install 14.04, shim.efi.signed renamed <MAAS:Triaged> <maas (Ubuntu):Triaged by andreserl> <https://launchpad.net/bugs/1713795>
[18:46] <roaksoax> zdw: http://paste.ubuntu.com/25426656/ -> apply that to /usr/lib/python2.7/dist-packages/....
[18:47] <roaksoax> zdw: http://paste.ubuntu.com/25426656/ -> apply that to /usr/lib/python2.7/dist-packages/provisioningserver/boot/uefi.py and restart maas-clusterd
[18:57] <zdw> roaksoax: Trying it now, thanks
[20:27] <ed___> Hi MAAS people :) I was wondering if someone was around to help with what I hope is some simple mistake I'm making...
[20:28] <ed___> I have just set up MAAS on ubuntu server 16.04 as per the docs, but cannot select a rack controller when I'm trying to set up DHCP. no rack controller is showing in the dropdown.
[20:29] <ed___> I have successfully registered the rack controller and the Nodes page 'controllers' tab shows the controller as "Region and rack controller"
[21:12] <mimizone> do people use the yaml machien details produced by maas to do asset management? (when new device was installed / moved to another server / decommission, what version of firmware were in the past etc...)
[21:13] <ed___> at this point I can only say: probably :)
[21:14] <mimizone> I'd like suggestion of what tool could just ingest the yaml/json and allow me to do search easily
[21:15] <mimizone> ed___: thanks :)
[21:15] <ed___> depends hugely on what you want to represent the data as, what you'd want to search and probably more factors I can't think of...
[21:17] <ed___> we use elasticsearch and prometheus in logging/monitoring capacities, but I fear your data is not well suited to either. Eg not a log message (unless you somehow emit **changes** that were made), and it's not a time-series type metric etiher
[21:18] <ed___> probably dump it into a text file for a while when you make a change, see what sort of searches become common ;)
[21:20] <mimizone> yes. I'll look into what can index json stuff fairly easily out of the box... avoiding mongo if possible.
[22:02] <iatrou> using maas 2.2.2 and testing on a maas-deployed host a bunch of lxd containers. the host has an eth0 (static) and a br0, attached to eth1 (DHCP). LXD has been configured to use br0
[22:03] <iatrou> the container start correctly and they acquire DHCP addresses from MAAS (the dhcp offer shows up in syslog)
[22:04] <iatrou> But when I query which IPs maas knows (maas admin subnet ip-addresses)  the IP addresses allocated to LXD do not show up
[22:41] <zdw> roaksoax: The patch you provided earlier today works properly
[22:41] <zdw> roaksoax: Thanks!