[04:16] <param> how to set servers to pxe boot
[04:17] <param> hello anyone there
[12:24] <voidspace> how do you edit the cluster interface in maas 2.0?
[12:27] <mup> Bug #1554494 opened: Preparation of RegionAdvertisingService failed: MultipleObjectsReturned: Got more than one node <MAAS:Triaged> <https://launchpad.net/bugs/1554494>
[12:28] <roaksoax> voidspace: http://maas.ubuntu.com/docs2.0/rack-configuration.html
[12:28] <roaksoax> voidspace: you don't
[12:28] <roaksoax> at least not in the same way people used to
[12:31] <voidspace> roaksoax: ah, ok - I'm trying to enlist nodes
[12:31] <voidspace> will read these docs, I was reading the development trunk ones... which are obviously for 1.9 then
[12:31] <roaksoax> voidspace: http://maas.ubuntu.com/docs2.0/rack-configuration.html#enabling-a-rack-controller-to-provide-dhcp-on-a-vlan
[12:31] <voidspace> roaksoax: great
[12:38] <voidspace> roaksoax: the nodes page says "maas maas nodes accept-all" to enable auto-enlist
[12:38] <voidspace> roaksoax: the command line tool says that accept-all is an invalid choice
[12:39] <voidspace> roaksoax: ah, they have appeared
[12:39] <voidspace> they were just slow, sorry
[12:48] <roaksoax> np!
[12:49] <roaksoax> voidspace: the 2.0 docs are ebing updated
[12:49] <roaksoax> so you will definietely find places wher eit doens't match or is incorrect
[12:51] <voidspace> roaksoax: I figured :-)
[13:27] <mup> Bug #1554514 opened: system_controller.py: AttributeError: 'NoneType' object has no attribute 'addBoth' <MAAS:Triaged> <https://launchpad.net/bugs/1554514>
[14:03] <mup> Bug #1554530 opened: Failed to update this region's process and endpoints: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554530>
[14:03] <mup> Bug #1554532 opened: Database error during start-up: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554532>
[14:22] <mup> Bug #1554530 changed: Failed to update this region's process and endpoints: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554530>
[14:22] <mup> Bug #1554532 changed: Database error during start-up: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554532>
[14:25] <mup> Bug #1554530 opened: Failed to update this region's process and endpoints: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554530>
[14:25] <mup> Bug #1554532 opened: Database error during start-up: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554532>
[15:31] <mup> Bug #1554566 opened: [2.0a1] PXE interface is incorrectly determined <MAAS:New> <https://launchpad.net/bugs/1554566>
[15:31] <mup> Bug #1554568 opened: [2.0a1] Can't look at full node event log: No item with pk: events <MAAS:New> <https://launchpad.net/bugs/1554568>
[17:19] <mimizone> is there a changelog of what maas 2.0 brings, at least the main features and the change of architecture and underlying technologies?
[17:21] <mimizone> and will it be an LTS release too?
[17:29] <voidspace> when I try to commission a KVM instance with 2.0 I get "modproble: ERROR: could not insert ipmi_si: no such device"
[17:29] <voidspace> The requested URL returned error: 400 BAD REQUEST
[17:29] <voidspace> failed to enlist system maas server
[17:29] <voidspace> any ideas why?
[17:30] <roaksoax> mimizone: have you looked into maas.ubuntu.com/docs2.0/changelog.html ?
[17:30] <voidspace> ah, maybe I need libvirt on the maas controller
[17:32] <mimizone> roaksoax: thanks. I couldn't find that page by just browsing the maas web page somehow.
[17:34] <voidspace> no, that didn't fix it
[17:43] <voidspace> roaksoax: blake_r: any idea about the ipm_si / BAD REQUEST problem above?
[17:43] <roaksoax> voidspace: ipmi_si, is that a IPMI based machine ?
[17:44] <voidspace> roaksoax: the maas controller and the nodes I'm enlisting are KVM instances
[17:44] <voidspace> roaksoax: which is another way of saying, I have no idea...
[17:44] <roaksoax> voidspace: ok, so the ipmi_si is just saying that you dont have IPMI
[17:44] <roaksoax> voidspace: which is correct
[17:44] <roaksoax> voidspace: the 400 BAD REQUEST, is the rack controller up and running successfully ?
[17:45] <voidspace> roaksoax: as far as I can tell - how would I check? The web ui seems to indicate everything is ok as far as I can see.
[17:46] <roaksoax> voidspace: check the log /var/log/maas/*.log
[17:47] <voidspace> ooh - rackd.log
[17:47] <voidspace> 2016-03-08 17:36:15+0000 [HTTPPageGetter,client] Starting TFTP back-end failed.
[17:47] <voidspace> quite a few of that
[17:48] <roaksoax> voidspace: check the rack controller page, and check the interfaces section and see if they are all correct and keep disappearing
[17:49] <voidspace> roaksoax: there a traceback in regiond.log as well
[17:49] <voidspace> pastebinning
[17:49] <voidspace> roaksoax: http://pastebin.ubuntu.com/15329173/
[17:50] <voidspace> rack controller page looks good
[17:50] <voidspace> there is an unused interface on the KVM image which apears there as an "unconfigured" interface
[17:50] <voidspace> maybe I should delete that
[18:04] <voidspace> roaksoax: so a vanilla install had set the maas-rack-controller api url to localhost
[18:04] <voidspace> roaksoax: I suspect that was the cause of the error, I've done dpkg-reconfigure and am trying again
[18:04] <voidspace> not sure though
[18:10] <mup> Bug #1554636 opened: maas serving old image to nodes <MAAS:New> <https://launchpad.net/bugs/1554636>
[18:22] <mup> Bug #1554636 changed: maas serving old image to nodes <MAAS:New> <https://launchpad.net/bugs/1554636>
[18:25] <mup> Bug #1554636 opened: maas serving old image to nodes <MAAS:New> <https://launchpad.net/bugs/1554636>
[18:37] <roaksoax> v1k0d3n: that may be it
[20:44] <mup> Bug #1554710 opened: MAAS 2.0alpha doesn't show imported images for commissioning <MAAS:New> <https://launchpad.net/bugs/1554710>
[21:47] <mup> Bug #1554747 opened: CPU Utilization of postgresql thread reaches 100% for deleting a node from MaaS <MAAS:New> <https://launchpad.net/bugs/1554747>
[22:04] <roaksoax> 4/win 4