[00:09] <mup> Bug #1629142 opened: 2.1 DHCP reported as enabled but not running <cdo-qa> <cdo-qa-blocker> <MAAS:Incomplete> <https://launchpad.net/bugs/1629142>
[00:10] <Marouen> Hi all
[00:11] <Marouen> Can I ask a question about how to import a windows image to MAAS 2.0 plz
[09:29] <KpuCko> hello, is it there any way to remove slave cluster from maas which is alredy down?
[09:30] <KpuCko> i can't remove it from web interface, im gettings clashes with MAAS DHCP and cannot remove interfaces, cannot change any state of cluster
[09:31] <KpuCko> when i do delete cluster slave i've got - unable to connect to cluster 'Cluster slave' (bdd58bfb-8
[11:34] <hbogert1> Is it easy to add some packages to the default ubuntu install? Or do I need to make a complete new deploy image for that?
[12:55] <mup> Bug #1625636 changed: [2.1] bridge_all on allocate needs to bridge all unconfigured interfaces too <juju> <MAAS:Invalid> <https://launchpad.net/bugs/1625636>
[12:56] <roaksoax> 3/win 9
[13:22] <myeagleflies> hello
[13:38] <shubjero> hi myeagleflies
[13:43] <baldpope> good morning all - shubjero working through networking setup - were you following the juju guide on insights.ubuntu.com?
[13:44] <shubjero> Nope, havent followed any juju guides.
[14:02] <myeagleflies> I have been trying to bootstrap juju on vm under vmware for last couple of hours. hopefully this works eventually ;)
[14:05] <myeagleflies> how long can it take for juju bootstrap to finish?
[14:12] <myeagleflies> es/node-ac7984ea-8589-11e6-94af-000c29c55c7f/
[14:12] <myeagleflies> 2016-09-30 14:09:58 ERROR juju.cmd supercommand.go:429 failed to bootstrap environment: bootstrap instance started but did not change to Deployed state: instance "/MAAS/api/1.0/nodes/node-ac7984ea-8589-11e6-94af-000c29c55c7f/" is started but not deployed
[14:13] <roaksoax> myeagleflies: has the machine deployed in MAAS ?
[14:14] <myeagleflies> no, it says 'Deploying'
[14:14] <roaksoax> myeagleflies: if you try to deploy your machine manually, does it deploy at all ?
[14:14] <myeagleflies> let me see
[14:15] <myeagleflies> deploying 16.04
[14:15] <myeagleflies> Maas uses 14.04
[14:16] <roaksoax> myeagleflies: right, so your machine is still in 'deploying' and has not changed to  'deployed'
[14:17] <roaksoax> myeagleflies: even if you deploy it manually (without juju)
[14:19] <myeagleflies> let's wait bit longer. the machine I've just started deploying is doing it right now
[14:19] <myeagleflies> (I've rebooted it manually to kick it off)
[14:19] <baldpope> myeagleflies, what's on the console of the vm your trying to deploy, anything?
[14:19] <myeagleflies> yep, it should various packaged being downloaded from ubuntu
[14:20] <myeagleflies> it is showing
[14:20] <baldpope> is there any way to suppress maas output, like if I'm scripting it?
[14:20] <baldpope> short of redirecting output to null
[14:21] <roaksoax> baldpope: what are you trying to suppress ? installation of the package itself ?
[14:22] <baldpope> sorry, no.. maas blah interface create-vlan $node blal blah ...
[14:22] <baldpope> the output of that
[14:25] <roaksoax> baldpope: nope, you could pipe it thoug
[14:26] <baldpope> thanks roaksoax - just making sure
[14:28] <myeagleflies> the host I was manually deploying finished just fine. it seems the trick was to manually reboot it
[14:28] <myeagleflies> now trying to deploy juju once more
[14:31] <roaksoax> myeagleflies: have power parameters not configiured for your machine ?
[14:31] <myeagleflies> I have them configured and set to vmware but it seems there was some issue. anyway watching how it proceeds this time
[14:37] <mup> Bug #1511589 changed: maas provider, hwclock out of sync means juju will not work <hs-arm64> <landscape> <maas-provider> <oil> <cloud-init:Confirmed> <curtin:Triaged> <falkor:Fix Released by tribaal> <juju-core:Invalid> <MAAS:Fix Released by allenap> <https://launchpad.net/bugs/1511589>
[14:43] <myeagleflies> roaksoax: there is some progress:
[14:44] <myeagleflies> - host is deployed now
[14:44] <myeagleflies> juju-gui deployment request accepted
[14:44] <myeagleflies> exposing service juju-gui
[14:44] <myeagleflies> 10:42:27 DEBUG juju:161 API message: --> {"Request": "ServiceExpose", "Params": {"ServiceName": "juju-gui"}, "Type": "Client", "RequestId": 2}
[14:44] <myeagleflies> however this failed with:
[14:44] <myeagleflies> 10:42:27 DEBUG juju:172 API message: <--
[14:44] <myeagleflies> Traceback (most recent call last):
[14:44] <myeagleflies> ..
[14:45] <myeagleflies>   File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
[14:45] <myeagleflies>     raise ValueError("No JSON object could be decoded")
[14:45] <myeagleflies> ValueError: No JSON object could be decoded
[14:46] <mup> Bug #1511589 opened: maas provider, hwclock out of sync means juju will not work <hs-arm64> <landscape> <maas-provider> <oil> <cloud-init:Confirmed> <curtin:Triaged> <falkor:Fix Released by tribaal> <juju-core:Invalid> <MAAS:Fix Released by allenap> <https://launchpad.net/bugs/1511589>
[14:55] <mup> Bug #1511589 changed: maas provider, hwclock out of sync means juju will not work <hs-arm64> <landscape> <maas-provider> <oil> <cloud-init:Confirmed> <curtin:Triaged> <falkor:Fix Released by tribaal> <juju-core:Invalid> <MAAS:Fix Released by allenap> <https://launchpad.net/bugs/1511589>
[15:14] <baldpope> roaksoax, i think I fopund a bug with maas client -
[15:15] <baldpope> I ran the following: maas test interface link-subnet $node eth4.100 subnet=cidr:10.100.0.0/20 mode=static ip=10.100.0.113
[15:15] <baldpope> but when I browse that node in maas webui, the staic IP is 10.100.0.103
[15:16] <baldpope> correction, static ip is 10.100.102
[15:25] <mup> Bug #1628331 changed: 21a4:Unhandled failure during AMP request <cdo-qa> <MAAS:Triaged> <https://launchpad.net/bugs/1628331>
[15:44] <baldpope> kiko hadn't been around for awhile
[16:26] <mup> Bug #1629384 opened: Need to retry on failure when releasing <MAAS:Triaged> <https://launchpad.net/bugs/1629384>
[16:31] <batkins61> Question.  New 2.0 MAAS setup.  Gui and CLI has very little in common with documentation.  Where can I go to get current 2.0 on 16.04.1 maas user documentation?
[16:33] <batkins61> Problem, server boots from MAAS (says under maas control), but never shows up in GUI under Nodes.  Any help on that?
[16:41] <batkins61> Is this the right place to ask questions about using maas?
[16:46] <brendand> batkins61, yes
[16:46] <brendand> batkins61, http://maas.io/docs. can you describe what the inconsistencies are? there are some known discrepancies so it would be helpful to be specific
[16:55] <batkins61> The docs tell you to add a network, and there is no discussion of fabrics or spaces.  The example screen shots are completely different.
[16:57] <brendand> batkins61, do you have  a link to the exact page?
[16:57] <batkins61> The problem I'm facing is that the node boots and comes up with "maas-enlisting-node", but never shows up under nodes
[16:57] <batkins61> http://maas.io/docs/installconfig-network2
[16:57] <brendand> batkins61, you shouldn't *have* to add any networks
[16:58] <brendand> ooh. that is definitely an old page
[16:58] <brendand> roaksoax, that section needs to be removed from the docs i think ^
[16:58] <batkins61> I assumed I messed up the network config, since I have the problem where nodes boot, but don't show up in the GUI.
[16:58] <batkins61> I'm using an external DHCP server, pointing to the maas server.
[17:05] <roaksoax> we need a bug filed and raised to the doc team
[17:23] <mup> Bug #1629394 opened: MAAS networks section needs to be removed from 2.0 docs <doc> <maasgh> <MAAS:New> <https://launchpad.net/bugs/1629394>
[17:53] <mup> Bug #1629402 opened: [2.1] please cleanup log format for new interface monitoring state <MAAS:New for mpontillo> <https://launchpad.net/bugs/1629402>
[18:10] <baldpope> roaksoax and brendand i write a lot of the technical doc internally for our company - do you guys want/need some help with documentation?
[18:10] <baldpope> i'm still new to maas myself, but not afraid of putting some text on paper
[19:15] <shubjero> Hey all, I'm SSH'ing to a jump server and using ipmiconsole to connect to a servers serial-over-lan and trying to enter the raid bios (ctrl-r) but ctrl-r seems to 'redraw/refresh' the ipmiconsole screen. Any idea on how I can pass the 'CTRL-R' keystroke to the server?
[19:34] <baldpope> some thick clients will have special macro menu commands for stuff like that
[19:37] <shubjero> yeah i know.. which is pretty handy.. but that doesnt exist for ipmiconsole
[19:38] <mup> Bug #1629430 opened: [UI] status messages on the Nodes page are in the wrong tense <MAAS:New> <https://launchpad.net/bugs/1629430>
[19:56] <roaksoax> baldpope: that'd be awesome if you could contribute to the docs
[19:56] <roaksoax> baldpope: our docs were neglected for so long, and we now have people working on them but there's so much they can do
[20:28] <baldpope> roaksoax, I'm catching up on my own install, but I've been compiling some notes based on documentation I've read throuhg
[20:29] <baldpope> once I'm 'done' I'll take a peak and look more officially at contributing
[20:39] <roaksoax> baldpope: awesome!
[20:45] <cmart> Howdy y'all. I'm trying to limit MAAS' DHCP scope. it's handing out addresses that conflict with other static IPs on the subnet we're using for provisioning.
[20:46] <cmart> What's the best way to tell MAAS "only hand out IP addresses in this specific range"? It looks like my colleague configured a reserved dynamic range, but either that didn't have an effect or we're not understanding it correctly.
[20:46] <smgoller> hey, does anyone has a jq snippet or something for pulling the physical interface names and mac addresses from nodes?
[20:47] <smgoller> the UI doesn't seem to show that info, but it's present in the json dumped from 'nodes read' via the cli
[21:12] <mup> Bug #1320074 changed: maas-import-pxe fails to catch comms errors when downloading UEFI shim and TBs instead <maas> <pxe> <server-hwe> <MAAS:Invalid> <maas (Ubuntu):New> <https://launchpad.net/bugs/1320074>
[21:12] <mup> Bug #1401840 changed: Number of nodes deployed per image showing incorrect values <oil> <MAAS:Invalid by blake-rouse> <https://launchpad.net/bugs/1401840>
[21:33] <mup> Bug #1320074 changed: maas-import-pxe fails to catch comms errors when downloading UEFI shim and TBs instead <maas> <pxe> <server-hwe> <MAAS:Invalid> <maas (Ubuntu):Won't Fix> <https://launchpad.net/bugs/1320074>
[22:39] <mup> Bug #1629475 opened: [2.1 ipv6] DNS generation should not fail when address-family conflicts are present <maas-ipv6> <MAAS:New> <https://launchpad.net/bugs/1629475>