/srv/irclogs.ubuntu.com/2016/03/08/#maas.txt

paramhow to set servers to pxe boot04:16
paramhello anyone there04:17
voidspacehow do you edit the cluster interface in maas 2.0?12:24
mupBug #1554494 opened: Preparation of RegionAdvertisingService failed: MultipleObjectsReturned: Got more than one node <MAAS:Triaged> <https://launchpad.net/bugs/1554494>12:27
roaksoaxvoidspace: http://maas.ubuntu.com/docs2.0/rack-configuration.html12:28
roaksoaxvoidspace: you don't12:28
roaksoaxat least not in the same way people used to12:28
voidspaceroaksoax: ah, ok - I'm trying to enlist nodes12:31
voidspacewill read these docs, I was reading the development trunk ones... which are obviously for 1.9 then12:31
roaksoaxvoidspace: http://maas.ubuntu.com/docs2.0/rack-configuration.html#enabling-a-rack-controller-to-provide-dhcp-on-a-vlan12:31
voidspaceroaksoax: great12:31
voidspaceroaksoax: the nodes page says "maas maas nodes accept-all" to enable auto-enlist12:38
voidspaceroaksoax: the command line tool says that accept-all is an invalid choice12:38
voidspaceroaksoax: ah, they have appeared12:39
voidspacethey were just slow, sorry12:39
roaksoaxnp!12:48
roaksoaxvoidspace: the 2.0 docs are ebing updated12:49
roaksoaxso you will definietely find places wher eit doens't match or is incorrect12:49
voidspaceroaksoax: I figured :-)12:51
mupBug #1554514 opened: system_controller.py: AttributeError: 'NoneType' object has no attribute 'addBoth' <MAAS:Triaged> <https://launchpad.net/bugs/1554514>13:27
mupBug #1554530 opened: Failed to update this region's process and endpoints: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554530>14:03
mupBug #1554532 opened: Database error during start-up: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554532>14:03
mupBug #1554530 changed: Failed to update this region's process and endpoints: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554530>14:22
mupBug #1554532 changed: Database error during start-up: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554532>14:22
mupBug #1554530 opened: Failed to update this region's process and endpoints: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554530>14:25
mupBug #1554532 opened: Database error during start-up: deadlock detected <MAAS:Triaged> <https://launchpad.net/bugs/1554532>14:25
mupBug #1554566 opened: [2.0a1] PXE interface is incorrectly determined <MAAS:New> <https://launchpad.net/bugs/1554566>15:31
mupBug #1554568 opened: [2.0a1] Can't look at full node event log: No item with pk: events <MAAS:New> <https://launchpad.net/bugs/1554568>15:31
mimizoneis there a changelog of what maas 2.0 brings, at least the main features and the change of architecture and underlying technologies?17:19
mimizoneand will it be an LTS release too?17:21
voidspacewhen I try to commission a KVM instance with 2.0 I get "modproble: ERROR: could not insert ipmi_si: no such device"17:29
voidspaceThe requested URL returned error: 400 BAD REQUEST17:29
voidspacefailed to enlist system maas server17:29
voidspaceany ideas why?17:29
roaksoaxmimizone: have you looked into maas.ubuntu.com/docs2.0/changelog.html ?17:30
voidspaceah, maybe I need libvirt on the maas controller17:30
mimizoneroaksoax: thanks. I couldn't find that page by just browsing the maas web page somehow.17:32
voidspaceno, that didn't fix it17:34
voidspaceroaksoax: blake_r: any idea about the ipm_si / BAD REQUEST problem above?17:43
roaksoaxvoidspace: ipmi_si, is that a IPMI based machine ?17:43
voidspaceroaksoax: the maas controller and the nodes I'm enlisting are KVM instances17:44
voidspaceroaksoax: which is another way of saying, I have no idea...17:44
roaksoaxvoidspace: ok, so the ipmi_si is just saying that you dont have IPMI17:44
roaksoaxvoidspace: which is correct17:44
roaksoaxvoidspace: the 400 BAD REQUEST, is the rack controller up and running successfully ?17:44
voidspaceroaksoax: 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:45
roaksoaxvoidspace: check the log /var/log/maas/*.log17:46
voidspaceooh - rackd.log17:47
voidspace2016-03-08 17:36:15+0000 [HTTPPageGetter,client] Starting TFTP back-end failed.17:47
voidspacequite a few of that17:47
roaksoaxvoidspace: check the rack controller page, and check the interfaces section and see if they are all correct and keep disappearing17:48
voidspaceroaksoax: there a traceback in regiond.log as well17:49
voidspacepastebinning17:49
voidspaceroaksoax: http://pastebin.ubuntu.com/15329173/17:49
voidspacerack controller page looks good17:50
voidspacethere is an unused interface on the KVM image which apears there as an "unconfigured" interface17:50
voidspacemaybe I should delete that17:50
voidspaceroaksoax: so a vanilla install had set the maas-rack-controller api url to localhost18:04
voidspaceroaksoax: I suspect that was the cause of the error, I've done dpkg-reconfigure and am trying again18:04
voidspacenot sure though18:04
mupBug #1554636 opened: maas serving old image to nodes <MAAS:New> <https://launchpad.net/bugs/1554636>18:10
mupBug #1554636 changed: maas serving old image to nodes <MAAS:New> <https://launchpad.net/bugs/1554636>18:22
mupBug #1554636 opened: maas serving old image to nodes <MAAS:New> <https://launchpad.net/bugs/1554636>18:25
roaksoaxv1k0d3n: that may be it18:37
mupBug #1554710 opened: MAAS 2.0alpha doesn't show imported images for commissioning <MAAS:New> <https://launchpad.net/bugs/1554710>20:44
mupBug #1554747 opened: CPU Utilization of postgresql thread reaches 100% for deleting a node from MaaS <MAAS:New> <https://launchpad.net/bugs/1554747>21:47
roaksoax4/win 422:04

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!