[00:08] is this channel logged? [00:08] 1 -> is there a mechanism for running an arbitrary script on node start-up (eg, user-data) [00:09] 2 -> what are MaaS physical zone's all about? [00:21] 3 -> what causes a node to move from "deploying" state to the next successful state? I've got ssh access to the host and so far as I can tell it's all fine, however it sits in "deploying" for a super long time then moves to "deploy failed" even though the server seems fine [00:46] Bug #1441399 was opened: socket.error: [Errno 92] Protocol not available [01:22] Bug #1441403 was opened: 1.8b1 Filter by zone is missing [01:22] Bug #1441404 was opened: 1.8b1 Accessing nodes detail page gets stuck in Loading [01:22] Bug #1441405 was opened: PXE power-off instead of power controller [01:52] Bug #1441408 was opened: 1.8b1 Failed Commissioning Machines are not turned off automatically after they timeout [04:28] Bug #1418157 changed: Install failed: Unexpected EOF in archive [07:44] Bug #1441467 was opened: Adding a node in the UI requires specifying a power controller [07:44] Bug #1441471 was opened: MAAS python-vmomi power type: can't "add chassis" twice [07:50] Bug #1441467 changed: Adding a node in the UI requires specifying a power controller [07:50] Bug #1441471 changed: MAAS python-vmomi power type: can't "add chassis" twice [07:56] Bug #1441467 was opened: Adding a node in the UI requires specifying a power controller [07:56] Bug #1441471 was opened: MAAS python-vmomi power type: can't "add chassis" twice [07:56] Bug #1441472 was opened: mass-cli "nodes new" command: autodetect_nodegroup parameter is undocumented [07:59] Bug #1441472 changed: mass-cli "nodes new" command: autodetect_nodegroup parameter is undocumented [08:14] Bug #1441472 was opened: mass-cli "nodes new" command: autodetect_nodegroup parameter is undocumented [08:44] Bug #1441497 was opened: DNS in deployed nodes not set correctly [08:56] Bug #1441497 changed: DNS in deployed nodes not set correctly [09:05] Bug #1441497 was opened: DNS in deployed nodes not set correctly === CyberJacob is now known as zz_CyberJacob [11:38] Bug #1441467 changed: Adding a node in the UI requires specifying a power controller [12:51] Bug #1441606 was opened: Error: Page not found The requested URL /MAAS/nodes/ was not found on this server. [12:51] Bug #1441610 was opened: 1.8b1 Machines get stuck in releasing for a long time [12:57] Bug #1441612 was opened: 1.8b1 Red outline on node name [13:09] Bug #1441612 changed: 1.8b1 Red outline on node name [13:21] Bug #1441612 was opened: 1.8b1 Red outline on node name [13:27] Bug #1441621 was opened: 1.8b1 Padding between edit node name and save button [13:27] Bug #1441624 was opened: MAAS doesn't support using an upstream proxy [14:39] Bug #1441652 was opened: 1.8b1: 502 Proxy Error when trying to access MAAS in browser [14:39] Bug #1441653 was opened: 1.8 V1: juju bootstrap failed - got error back from server: 502 Proxy Error [15:09] Bug #1441653 changed: 1.8 V1: juju bootstrap failed - got error back from server: 502 Proxy Error [15:09] Bug #1441682 was opened: 1.8beta1: RAM units is given as GB on node details page, instead of GiB [15:21] Bug #1441684 was opened: Add test for SO_REUSEPORT and add warning log if kernel does not support it [15:21] Bug #1441686 was opened: 1.8beta1: Storage sizes displayed as floating point [15:33] Bug #1441684 changed: Add test for SO_REUSEPORT and add warning log if kernel does not support it [15:33] Bug #1441686 changed: 1.8beta1: Storage sizes displayed as floating point [15:39] Bug #1441684 was opened: Add test for SO_REUSEPORT and add warning log if kernel does not support it [15:39] Bug #1441686 was opened: 1.8beta1: Storage sizes displayed as floating point [17:27] Bug #1441756 was opened: Manager service is not sending limit to region [17:39] Bug #1441756 changed: Manager service is not sending limit to region [17:42] Bug #1441756 was opened: Manager service is not sending limit to region === bladernr` is now known as bladernr_ === zz_CyberJacob is now known as CyberJacob [19:37] hi, how can I assign static IPs to servers, aka mac addresses? I want to manually assign them...anyone have pointers on doing that with maas? [19:41] serverascode: only available in MAAS 1.7 or 1.8b1+ [19:41] serverascode: maas admin node claim-sticky-ip-address [19:41] serverascode: maas admin node claim-sticky-ip-address --help [19:41] ok cool thanks will chekc that out [20:28] Bug #1441837 was opened: [1.8b1 devices] Can't add a device with multiple NIC's [20:28] Bug #1441841 was opened: [1.8b1 devices] Can't add a device that has IP address that it is within the wider range MAAS manages, but not within Dynamic/Static range MAAS manages [21:10] Bug #1441851 was opened: 1.8b1: Can't view list of nodes for a physical zone [21:25] Bug #1441851 changed: 1.8b1: Can't view list of nodes for a physical zone [21:28] Bug #1436277 changed: No error message when the websocket connection times out [21:28] Bug #1441864 was opened: 1.8b1: Can't filter servers by owner correctly if owner is subset of another owner [23:55] Bug #1441472 changed: mass-cli "nodes new" command: autodetect_nodegroup parameter is undocumented