[00:09] Bug #1629142 opened: 2.1 DHCP reported as enabled but not running

[00:10] Hi all [00:11] Can I ask a question about how to import a windows image to MAAS 2.0 plz === frankban|afk is now known as frankban === mup_ is now known as mup === mup_ is now known as mup === bbaqar_ is now known as bbaqar === mup_ is now known as mup === frankban is now known as frankban|afk [09:29] hello, is it there any way to remove slave cluster from maas which is alredy down? [09:30] 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] when i do delete cluster slave i've got - unable to connect to cluster 'Cluster slave' (bdd58bfb-8 === frankban|afk is now known as frankban === bbaqar__ is now known as bbaqar [11:34] 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] Bug #1625636 changed: [2.1] bridge_all on allocate needs to bridge all unconfigured interfaces too [12:56] 3/win 9 [13:22] hello [13:38] hi myeagleflies [13:43] good morning all - shubjero working through networking setup - were you following the juju guide on insights.ubuntu.com? [13:44] Nope, havent followed any juju guides. [14:02] I have been trying to bootstrap juju on vm under vmware for last couple of hours. hopefully this works eventually ;) [14:05] how long can it take for juju bootstrap to finish? [14:12] es/node-ac7984ea-8589-11e6-94af-000c29c55c7f/ [14:12] 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] myeagleflies: has the machine deployed in MAAS ? [14:14] no, it says 'Deploying' [14:14] myeagleflies: if you try to deploy your machine manually, does it deploy at all ? [14:14] let me see [14:15] deploying 16.04 [14:15] Maas uses 14.04 [14:16] myeagleflies: right, so your machine is still in 'deploying' and has not changed to 'deployed' [14:17] myeagleflies: even if you deploy it manually (without juju) [14:19] let's wait bit longer. the machine I've just started deploying is doing it right now [14:19] (I've rebooted it manually to kick it off) [14:19] myeagleflies, what's on the console of the vm your trying to deploy, anything? [14:19] yep, it should various packaged being downloaded from ubuntu [14:20] it is showing [14:20] is there any way to suppress maas output, like if I'm scripting it? [14:20] short of redirecting output to null [14:21] baldpope: what are you trying to suppress ? installation of the package itself ? [14:22] sorry, no.. maas blah interface create-vlan $node blal blah ... [14:22] the output of that [14:25] baldpope: nope, you could pipe it thoug [14:26] thanks roaksoax - just making sure [14:28] the host I was manually deploying finished just fine. it seems the trick was to manually reboot it [14:28] now trying to deploy juju once more [14:31] myeagleflies: have power parameters not configiured for your machine ? [14:31] I have them configured and set to vmware but it seems there was some issue. anyway watching how it proceeds this time [14:37] Bug #1511589 changed: maas provider, hwclock out of sync means juju will not work

[14:43] roaksoax: there is some progress: [14:44] - host is deployed now [14:44] juju-gui deployment request accepted [14:44] exposing service juju-gui [14:44] 10:42:27 DEBUG juju:161 API message: --> {"Request": "ServiceExpose", "Params": {"ServiceName": "juju-gui"}, "Type": "Client", "RequestId": 2} [14:44] however this failed with: [14:44] 10:42:27 DEBUG juju:172 API message: <-- [14:44] Traceback (most recent call last): [14:44] .. [14:45] File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode [14:45] raise ValueError("No JSON object could be decoded") [14:45] ValueError: No JSON object could be decoded [14:46] Bug #1511589 opened: maas provider, hwclock out of sync means juju will not work

[14:55] Bug #1511589 changed: maas provider, hwclock out of sync means juju will not work

[15:14] roaksoax, i think I fopund a bug with maas client - [15:15] 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] but when I browse that node in maas webui, the staic IP is 10.100.0.103 [15:16] correction, static ip is 10.100.102 [15:25] Bug #1628331 changed: 21a4:Unhandled failure during AMP request [15:44] kiko hadn't been around for awhile === frankban is now known as frankban|afk [16:26] Bug #1629384 opened: Need to retry on failure when releasing [16:31] 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] Problem, server boots from MAAS (says under maas control), but never shows up in GUI under Nodes. Any help on that? [16:41] Is this the right place to ask questions about using maas? [16:46] batkins61, yes [16:46] 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] 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] batkins61, do you have a link to the exact page? [16:57] 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] http://maas.io/docs/installconfig-network2 [16:57] batkins61, you shouldn't *have* to add any networks [16:58] ooh. that is definitely an old page [16:58] roaksoax, that section needs to be removed from the docs i think ^ [16:58] 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] I'm using an external DHCP server, pointing to the maas server. [17:05] we need a bug filed and raised to the doc team [17:23] Bug #1629394 opened: MAAS networks section needs to be removed from 2.0 docs [17:53] Bug #1629402 opened: [2.1] please cleanup log format for new interface monitoring state [18:10] 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] i'm still new to maas myself, but not afraid of putting some text on paper [19:15] 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] some thick clients will have special macro menu commands for stuff like that [19:37] yeah i know.. which is pretty handy.. but that doesnt exist for ipmiconsole [19:38] Bug #1629430 opened: [UI] status messages on the Nodes page are in the wrong tense [19:56] baldpope: that'd be awesome if you could contribute to the docs [19:56] 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] 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] once I'm 'done' I'll take a peak and look more officially at contributing [20:39] baldpope: awesome! [20:45] 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] 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] hey, does anyone has a jq snippet or something for pulling the physical interface names and mac addresses from nodes? [20:47] 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] Bug #1320074 changed: maas-import-pxe fails to catch comms errors when downloading UEFI shim and TBs instead

[21:12] Bug #1401840 changed: Number of nodes deployed per image showing incorrect values [21:33] Bug #1320074 changed: maas-import-pxe fails to catch comms errors when downloading UEFI shim and TBs instead

[22:39] Bug #1629475 opened: [2.1 ipv6] DNS generation should not fail when address-family conflicts are present