[04:27] <mup> Bug #1550510 changed: 1.9 UI Take action "Go" button for (re)commissioning a node with customized storage doesn't trigger the action <MAAS:Expired> <https://launchpad.net/bugs/1550510>
[10:17] <mup> Bug #1575567 opened: Re-commissioning doesn't detect storage changes <MAAS:New> <https://launchpad.net/bugs/1575567>
[10:47] <mup> Bug #1575587 opened: Can't add new machines <MAAS:New> <https://launchpad.net/bugs/1575587>
[10:47] <mup> Bug #1575590 opened: MAAS 1.9 docs contain out of date screenshots <MAAS:New> <https://launchpad.net/bugs/1575590>
[12:05] <mup> Bug #1575625 opened: Can't find way for MAAS to autodiscover IPMI settings <MAAS:New> <https://launchpad.net/bugs/1575625>
[12:35] <mup> Bug #1575631 opened: TestStaticIPAddressManagerMapping.test_get_hostname_ip_mapping_returns_domain_head_ips fails spuriously <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1575631>
[12:53] <DavidRama> Hi folks, can Maas set-up network ranges for the  interfaces on the hosts without having a NIC connected to them ?
[12:53] <DavidRama> them == network ranges
[13:05] <mup> Bug #1374447 changed: some dns queries not forwarded properly <MAAS:Invalid> <https://launchpad.net/bugs/1374447>
[13:43] <roaksoax> DavidRama: If you are using 1.9, you need to setup a static and dynamic range
[13:43] <roaksoax> DavidRama: the dynamic rnage is used for say, commissioning, or random machines obtaining IP's from MAAS
[13:43] <roaksoax> DavidRama: the static range is used for IP to be given to machines when deploying, statically
[13:43] <roaksoax> DavidRama: in 2.0+ the static range disappeared, the only one that remains is the dynamic range
[13:43] <roaksoax> DavidRama: which allows MAAS to enlist/commissioning using an IP from there
[13:44] <roaksoax> DavidRama: all machines you deploy, by default, will get an IP outside from static range
[14:14] <mup> Bug # opened: 1575692, 1575693, 1575696, 1575697
[14:59] <bugrum> I just installed MAAS 2.0 beta 3 on Ubuntu 16.04 LTS and I noticed that Wake on Lan is no longer an option in the Power Type dropdown when configuring nodes. Is Wake on Lan no longer supported on MAAS?
[16:05] <mup> Bug #1575697 changed: test 4 <ux> <MAAS:Invalid> <https://launchpad.net/bugs/1575697>
[18:00] <mup> Bug #1575815 opened: NIC previously discovered through commissioning no longer connected to Maas network <oil> <MAAS:New> <https://launchpad.net/bugs/1575815>
[20:07] <bdx> hey whats up everyone? I can't seem to get my region-controller to recognize my rack-controller ... any ideas? MAAS Version 2.0.0 (beta3+bzr4941)
[20:21] <mup> Bug #1533229 changed: 1.9 wily arm64 root-image fails to deploy on EFI system <curtin:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1533229>
[20:21] <mup> Bug #1547185 changed: backtrace in node.create_bcache <landscape> <MAAS:Invalid> <MAAS 1.9:Invalid> <https://launchpad.net/bugs/1547185>
[20:21] <mup> Bug #1548542 changed: maas.drivers.power.ipmi: [WARNING] Failed to change the boot order to PXE <IP>  ipmi_ctx_open_outofband_2_0: BMC busy on Dell 12G servers <oil> <MAAS:Won't Fix> <https://launchpad.net/bugs/1548542>
[20:21] <mup> Bug #1575910 opened: [2.0a4] Fabric and space lack a description field <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1575910>
[20:29] <bdx> Hey hows it going everyone? How can I add a rack controller? I have followed the procedure outlined in the docs, but my rack-controller and its supporting services are not showing up ....
[20:30] <bdx> I mean, I see a controller under my nodes tab, but when I select it, all of the rack-controller services are red
[20:30] <bdx> also, when I select the images tab, I see "One rack controller is not yet connected to the region. Visit the rack controllers page for more information." at the top of the page
[20:31] <bdx> can anyone lend some insight on how to get past this?
[20:31] <bdx> thanks
[20:33] <bdx> when I try to delete the skeleton rack-controller that exists, I get this -> http://paste.ubuntu.com/16088372/
[20:33] <bdx> ^SOS^
[20:39] <roaksoax> bdx: known bug, fixed in latest trunk
[20:39] <roaksoax> bdx: or soon to be beta4
[20:40] <bdx> roaksoax: can I upgrade to beta4 by using ppa:maas/devel ?
[20:40] <roaksoax> bdx: but that being said, what errors do you ssee in rackd.log in the rack that's failing to conect ?
[20:40] <roaksoax> blake_r: ^^
[20:40] <roaksoax> bdx: haven't released beat4 just yet
[20:41] <roaksoax> bdx: it will be tomorrow or friday
[20:41] <blake_r> bdx: what is in rackd.log?
[20:42] <blake_r> bdx: does it say its connecting?
[20:42] <blake_r> bdx: seems like it is not connection to the region
[20:43] <bdx> blake_r, roaksoax: http://paste.ubuntu.com/16088464
[20:45] <blake_r> bdx: okay its getting rejected by the regin
[20:45] <blake_r> bdx: whats in the regiond.log
[20:52] <bdx> blake_r, roaksoax: http://paste.ubuntu.com/16088545/
[20:56] <blake_r> mpontillo: ^ see the "Interface matching query does not exist"
[20:59] <mpontillo> bdx: can you post the content of "sudo maas-rack support-dump --networking" on the rack that is failing to register?
[21:00] <mpontillo> bdx: actually I bet I know what this is. if you've been upgrading through previous betas, you may have corrupted interfaces in your database. let me see if I can find the workaround
[21:01] <mpontillo> blake_r: see https://bugs.launchpad.net/maas/+bug/1563701/comments/13
[21:01] <mpontillo> bdx: ^ oops notified wrong person
[21:02] <roaksoax> blake_r: i wonder if his issues would go away with latest trunk ?
[21:02] <mpontillo> roaksoax: a fresh install would fix it if it's the issue I'm thinking of
[21:03] <mpontillo> roaksoax: previous beta users who have VLAN interfaces will hit this bug where they have incorrect interfaces stored in the datbaase
[21:03] <mpontillo> *database
[21:03] <mpontillo> that is, VLAN interfaces on rack controllers.
[21:03] <roaksoax> mpontillo: how do we clean that up though
[21:03] <mpontillo> roaksoax: we could do a database migration to do it.
[21:07] <roaksoax> mpontillo: yeah we might have to do that
[21:08] <mpontillo> roaksoax: it's a bit of a toss-up at this point, as it would only affect users of early betas
[21:15] <roaksoax> mpontillo: bhehe early beta1 nbeta2 or 3 ?
[21:16] <mpontillo> roaksoax: fixed in beta 2 I think
[21:32] <bdx> roaksoax, mpontillo, blake_r: `sudo maas-rack support-dump --networking` -> http://paste.ubuntu.com/16088880
[21:35] <bdx> mpontillo: could I manually replace the incorrect legacy interface values in the db?
[21:35] <bdx> what table should I be looking at here?
[21:36] <mpontillo> bdx: don't worry, I spotted the bug ;-) blake_r: take a look at the paste, it looks like get_interfaces_definition() is returning incorrect parents. the get_ip_addr() output is correct, but the VLANs' parents are themselves?!
[21:37] <mpontillo> bdx: are you able to file a bug?
[21:37] <bdx> mpontillo: have you identified the fix as well?
[21:37] <mpontillo> bdx: not yet
[21:37] <bdx> lol ... tis all I do
[21:38] <mpontillo> bdx: yeah the code is assuming the VLAN name format is "<parent>.<vid>" when in your case you are using the alternate format
[21:39] <mpontillo> bdx: https://paste.ubuntu.com/16088926/ <-- sad code
[21:40] <mpontillo> bdx: just FYI, the input into that function is the output of the top function in your paste, get_ip_addr(). so we actually have all the data we need to make this correct
[21:40] <bdx> mpontillo: I was in the middle of a workflow that I was trying to deploy/use xenial in, I upgraded my test-maas from 14.04 to 16.04 ... is there anything I can do to get things back to working real quick, or will I need to wait for the patch to land?
[21:40] <bdx> oh my
[21:40] <bdx> I see
[21:40] <bdx> ooh, hmm
[21:40] <mpontillo> bdx: should be a pretty easy fix.. let me see if I can get a quick patch for you to try
[21:46] <mpontillo> bdx: sudo patch -d /usr/lib/python3/dist-packages -i /tmp/patch -p1
[21:46] <mpontillo> bdx: given https://paste.ubuntu.com/16088969/ in /tmp/patch
[21:46] <mpontillo> bdx: can you tell me if that fixes it?
[21:46] <bdx> ha ya
[21:46] <bdx> that was super fast! nice!
[21:47] <mpontillo> bdx: hope it works =)
[21:47] <mpontillo> bdx: completely untested TBH, you are the guinea pig right now, just thought you might like a preview of the fix
[21:49] <bdx> mpontillo: should I dpkg-reconfigure maa-rack-controller following the application of the patch?
[21:50] <mpontillo> bdx: that should not be necessary, just restart the rackd service and tell me if it registers successfully
[21:51] <bdx> how?
[21:51] <bdx> oh, the twistd3 process?
[21:52] <bdx> oh maas-rackd
[21:52] <bdx> nm
[21:53] <bdx> oooooooOOOooo
[21:53] <bdx> Success!!!!
[21:53] <bdx> so sick
[21:53] <bdx> I bow to thee
[21:53] <bdx> mpontillo: real nice
[21:54] <mpontillo> bdx: awesome, thanks for testing it for us =)
[21:54] <bdx> np
[21:55] <roaksoax> mpontillo: that's fixed in trunk isn't it
[21:55] <roaksoax> ?
[21:56] <mpontillo> roaksoax: nope
[21:56] <mpontillo> roaksoax: we need a bug for this
[21:57] <bdx> I just made one
[21:58] <bdx> https://bugs.launchpad.net/maas/+bug/1575945
[22:01] <mup> Bug #1575945 opened: rack-controller not connecting <MAAS:New> <https://launchpad.net/bugs/1575945>
[22:01] <mup> Bug #1575946 opened: dist-upgrade from trusty to xenial errors (maas 1.9 -> 2.0) <landscape> <MAAS:New> <https://launchpad.net/bugs/1575946>
[22:03] <bdx> mpontillo: how can I get dhcp going on my maas-mgmt network again?
[22:03] <bdx> oh nm, I think I see
[22:06] <bdx> yea, actually, how do I configure dhcp?
[22:09] <bdx> I from what I can gather it is on, on the desired subnet, I just don't know how to introspect that from the gui ...?
[22:10] <bdx> ahh, ok, dhcp is active
[22:10] <bdx> on my maas-mgmt network ... I just don't see where or how. .... this must be upcoming gui functionality ?
[22:14] <mpontillo> bdx: that info is on the vlan details page; the range is on the subnet details page. Not all of it can be edited from the UI in the current beta
[22:14] <bdx> ok, I see
[22:15] <bdx> mpontillo, blake_r, roaksoax: thanks for your help today!
[22:22] <bdx> is maas2.0 not compatible with < juju2?
[22:31] <mup> Bug #1575951 opened: upgrade of maas from 1.9.1 to 2.0 'str' object has no attribute 'version' <landscape> <MAAS:New> <https://launchpad.net/bugs/1575951>
[22:55] <mpontillo> bdx: https://jujucharms.com/docs/devel/introducing-2#maas-2.0
[22:56] <mpontillo> bdx: sadly I don't think MAAS 2.0 support made it in time for Xenial; you may need a dev release of juju
[22:56] <mpontillo> bdx: I haven't tried it yet myself.
[22:57] <bdx> do I have to bootstrap with that flag set, or is it enough to just set it?
[22:57] <bdx> ok
[23:00] <mpontillo> bdx: I'd assume you would need to bootstrap with that, since bootstrap makes use of MAAS
[23:00] <mpontillo> IIRC ;-)
[23:01] <rp_> Any one have info on a replacement for image-builder?  seems to be deprecated and advised to use maas/main.