[00:09] <mup> Bug #1593487 opened: [2.0b7]maas-region-controller failed to preconfigure exit 127 <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1593487>
[00:44] <axisys> how do I pick the network interface on virtualbox for maas? I was thinking eth0 as bridge and eth1 as host-only and enable maas-dhcp on eth1.. does it sound right?
[00:49] <mpontillo> https://paste.ubuntu.com/17419813/ .. oh, thetrav left =(
[01:39] <mup> Bug #1593516 opened: docs2.0/ha juju deploy maas-region not correct syntax <MAAS:New> <https://launchpad.net/bugs/1593516>
[05:31] <ildar> hi again whoever unsleep
[05:31] <ildar> http://paste.ubuntu.com/17425807/
[05:33] <ildar> the problem is that after uninstallation error next installation stucks: it doesn't see "Ready" nodes and says "Not enough resources"
[08:51] <romilos> hello
[08:51] <romilos> I am trying to enlist a node but it stuck on login
[08:51] <romilos> I use pxe boot and it is a VM
[08:52] <romilos> and the node does not appears on maas interface
=== jacekn_ is now known as jacekn
[09:53] <romilos> yoooo
[09:54] <ildar> did the node boot with PXE?
[09:54] <romilos> y
[09:54] <romilos> and then it stays in login
[09:55] <ildar> login?
[09:55] <romilos> it find maas and the os installed
[09:55] <romilos> but then it stays at login
[09:55] <ildar> the hostname ?
[09:55] <romilos> it stays at ubuntu login:
[09:55] <ildar> no
[09:56] <ildar> it must have booted from the harddrive
[09:59] <romilos> i think it did not
[09:59] <romilos> it does not had any os pre-installed
[09:59] <romilos> anyway I try again and I have disable the harddrive
[10:04] <romilos> it happens the same again it stays at login
[12:06] <D4RKS1D3> Hi
=== frankban is now known as frankban|afk
[12:24] <kiko> hey D4RKS1D3
[13:02] <mup> Bug #1593714 opened: [2.0, docs] DHCP start command documentation wrong for 2.0 <documentation> <MAAS:Confirmed> <https://launchpad.net/bugs/1593714>
[13:08] <D4RKS1D3> Hi kiko
[16:11] <mup> Bug #1593789 opened: [2.0RC1] Nodes API doesn't show regions <MAAS:New> <https://launchpad.net/bugs/1593789>
[20:03] <mup> Bug #1593856 opened: Need a way to surface a name for an api-key in logs <oil> <MAAS:New> <https://launchpad.net/bugs/1593856>
[21:33] <mup> Bug #1593881 opened: 2.0 beta7: Internal Server Error following installation <oil> <MAAS:New> <https://launchpad.net/bugs/1593881>
[21:36] <mup> Bug #1593881 changed: 2.0 beta7: Internal Server Error following installation <oil> <MAAS:New> <https://launchpad.net/bugs/1593881>
[21:42] <mup> Bug #1593881 opened: 2.0 beta7: Internal Server Error following installation <oil> <MAAS:New> <https://launchpad.net/bugs/1593881>
[23:43] <mup> Bug #1593393 opened: MAAS fails to commission if requested immediately after boot images downloaded <MAAS:New> <https://launchpad.net/bugs/1593393>