[00:38] any way to import the image from local disk to my VM MAAS running on VirtualBox on same bridge network [00:40] Marco has sudo maas-import-isos in http://marcoceppi.com/2012/05/juju-maas-virtualbox/ .. but i dont have that option on 14.04 [01:07] Running MAAS Version 2.0.0 (beta3+bzr4941) - maas is running and assigning IP addresses via DHCP. I PXE boot a node, it gets an IP address but then just stops and moves on to the next boot option with a “TFTP .” Any ideas what I am missing? It looks like maas is not setting a TFTP server for the PXE client to get tht image from [01:20] what do I configure maas dhcp on the virtualbox VM MAAS controller? I am guessing I need to add a second interface on host-only network and use that network subnet to make sure I dont break my host dhcp network? [01:21] wish it were explained anywhere in the internet.. [01:21] so much for the claim in the /topic ;-) === rharper` is now known as rharper [07:26] Bug #1592994 changed: MAAS end point cannot be added "HTTP 410 Error Gone"

=== huats_ is now known as huats === jacekn_ is now known as jacekn [13:18] Bug #1592757 changed: MAAS 1.9+ not picking up Mellanox ConnectX-4_EN 2x25Gbe card [13:18] Bug #1593219 opened: [CI] test_create_dynamic_range sometimes fails in CI === jhobbs_ is now known as jhobbs === dannf` is now known as dannf [16:46] Bug #1567249 opened: If rack and region have different versions, the error is uninformative and confusing [16:52] Bug #1593334 opened: Subnet add errors out on data valication [17:13] Bug #1593344 opened: [2.0b8] Dropdown shadow's have disappeared and dropdown mixes with background [17:43] Bug #1593334 changed: Subnet add errors out on data valication [18:53] Bug #1593377 opened: MAAS should recheck power status if it thinks a node is already on when commissioning/deploying [18:53] hi! anybody here? [18:54] I wonder: 2.0.0 doesn't have Clusters [18:54] so configuring interfaces became tricky [18:54] or not? [18:57] ildar: not really ? [18:57] ildar: what are you trying to do? [18:58] I just don't see howto set intterfaces [18:58] ildar: what do you mean by "set interfaceS" [18:58] in my case I have ens9 for provisioning [18:58] ildar: which is why I'm wondering what are you trying to do [18:59] but I don't see how do I tell MAAS it is ens9 [18:59] ildar: http://maas.ubuntu.com/docs2.0/rack-configuration.html#enabling-a-dhcp-on-a-vlan-optional-ha [19:00] Network tab doesn't show anything about ens9 [19:00] I made a vlan [19:00] but how it would find on which interface it is? [19:07] ildar, that comment is weird. a tagged vlan is created from a raw interface. [19:07] hm. I have untagged interface [19:08] then what do I do? "Provide DHCP" ? [19:08] ildar, yes, basically [19:09] ildar, so ens9 is.. the interface on the MAAS cluster controller, yes? [19:09] if so [19:09] what VLAN is it connected to [19:09] yes [19:09] and what network is it? [19:09] anyway, you just go to the VLAN and you serve DHCP on it [19:09] no vlans configured. Plain interface [19:09] if the cluster controller has an interface on that VLAN it will serve [19:09] ah [19:09] there is a nomenclature collission [19:09] err [19:09] colission [19:10] go to the networks tab [19:10] is there a vlan listed there? [19:10] does it look sane? [19:10] in the networks tab, where you read VLAN, think of it as a "L2 segment" [19:10] * kiko hears clicking clicking clicking [19:11] :) [19:11] 1 sec [19:13] ahh, I have my lab lagging [19:13] sorry [19:15] http://paste.ubuntu.com/17408804/ [19:16] http://paste.ubuntu.com/17408831/ [19:20] I created deploy-net, thought fabric-0 was autocreated. [19:20] deleting deploy-net now [19:22] so the fabric looks empty [19:23] Bug #1593388 opened: Changing a boot source URL while images are being download doesn't interrupt current downloads to use the new URL [19:29] Hm, I see. I seem to missed rack-controller registration [19:30] though the maas.io/get-started appears to be very misleading [19:30] I'll try the procedure, thanks for guiding [19:42] yeah, that doc needs a serious update [19:43] can't get MAAS see itself as a controller [19:43] :( [19:44] did that "$ sudo dpkg-reconfigure maas-rack-controller", no luck [19:45] still have "0 Controllers" [19:49] roaksoax, ^^ ? [20:09] hm [20:10] I see regiond.log polluted with http://paste.ubuntu.com/17410850/ [20:10] 44M , too much [20:10] it's a bug jim [20:11] mpontillo, ^^ [20:11] ildar, 1.9 or 2.0? [20:11] 2.0.0 [20:11] MAAS Version 2.0.0 (beta3+bzr4941) [20:11] ildar, could you update to the latest beta first? [20:12] it's the latest available from ppa [20:12] is not! [20:12] https://launchpad.net/~maas/+archive/ubuntu/next [20:12] at least it is two days old, not more [20:12] ildar: beta 7 should be available in ppa:maas/next [20:12] 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 [20:12] ahhh [20:13] what PPA are you using? [20:13] I see [20:13] * kiko frowns [20:13] ppa:maas/stable [20:13] should be stable and workable :) [20:14] * kiko updates the description of experimental [20:14] ildar: MAAS is still in beta on Xenial; there is no stable version per se. I think beta 3 is what ended up in the archive when Xenial was shipped [20:14] :) [20:14] ok [20:14] ildar: it should be quite usable though; we are nearing a release candidate based mostly on beta 7 [20:15] ildar, you are joking about maas/stable I think [20:15] but I can't update right now [20:15] as 2.0 is not in that PPA [20:15] you are using maas-maintainers/experimental [20:15] which has been deprecated [20:15] you should use maas/next [20:16] I'm NOT joking, the serious page http://www.ubuntu.com/download/cloud/install-openstack-with-autopilot says install maas/stable [20:16] ;) [20:16] ildar, if that is what you were using you'd be on 1.9.3 [20:17] ildar, so which is it? [20:17] ildar: if you want to use autopilot you probably want the stable version of MAAS, which is still trusty-based [20:17] ildar: so you want ppa:maas/stable on Ubuntu 14.04. sadly. =) everything should catch up soon... [20:17] ildar: ppa:maas/stable is 1.9 series [20:17] ildar: 2.0 series is ppa:maas/next [20:17] and second what mpontillo is saying [20:18] But that page doesn't explicitly says: Trusty [20:18] it doesn't need to [20:18] so I tried 1604 [20:18] I see the disconnect [20:18] ildar, you deployed 16.04 which shipped with maas 2 beta2 [20:18] kiko: yeah that is an oversight, thanks for pointing that out ildar [20:19] ildar, the stable PPA is not getting used because 1.9 is older than the version shipped in 16.04 [20:19] I see. [20:19] ildar, so you either need to redeploy with 14.04 and use 1.9, or use the experimental PPA and move on to 2.0. [20:19] ildar, if your objective is autopilot, then you want 1.9 and 14.04 everywhere. [20:19] I tried MAAS on Trusty BTW [20:20] MAAS worked finr [20:20] MAAS worked fine [20:20] sure it did! 1.9.3 is the bomb! [20:20] but openstack installer failed to see the Ready nodes [20:20] and if you had problems with autopilot then those are usually fixable :) [20:20] complaining that no nodes available [20:20] that's okay, we can probably get that fixed [20:21] there are a bunch of little issues with the first part of openstack-install [20:21] once landscape is running it's all good though [20:21] OK [20:21] anyway, ping us when you have 14.04 and 1.9.3 live [20:21] then I'll get my 1404 MAAS and get back to [20:21] that's a couple of minutes [20:22] I saved it just in case ;) [20:46] %&$*&*(&(*, my admin disabled internet access for the lab. [20:46] Is MAAS able to work standalone, without internet? [20:47] Commisioning seems stuck === spammy is now known as Guest95181 [20:49] Hello... === Guest95181 is now known as spammy [20:49] ahoy [20:50] I'm trying to conjure-up openstack, and I think I have some maas erros that might be causing it to fail. [20:52] what step is that? [20:52] Is this the place to ask? [20:52] sure! I'm doing the same here ;) [20:53] I've been following Ubuntu's how-to, but with 16.04. http://www.ubuntu.com/download/cloud/install-openstack-with-autopilot [20:53] :P [20:53] wrong [20:54] just knew that [20:54] I have a kind of working MAAS up using a 2interface controller and 4 nodes with 2 disks each. [20:54] lol [20:54] is there a better guide? [20:54] oh! you get more then I [20:54] no. Guys here say that you should use another ppa [20:55] ppa:maas/next namely [20:55] Yes, I had to use another ppa, hang on... [20:55] add-apt-repository ppa:maas-maintainers/experimental3 [20:57] hah [20:57] (2016-06-17 02:15:27) kiko: as 2.0 is not in that PPA [20:57] (2016-06-17 02:15:56) kiko: you are using maas-maintainers/experimental [20:57] (2016-06-17 02:16:00) kiko: which has been deprecated [20:57] (2016-06-17 02:16:05) kiko: you should use maas/next [20:57] is that that? [20:59] OK I'll give that a try. [20:59] I hope I gave the right advice [21:00] as I just received that information [21:00] and actually don't know much about MAAS [21:01] thanks [22:40] so, the disk wipe feature seems to take an extremely long time. What is the command MaaS actually executes here? [22:40] command / process / whatever [23:38] Bug #1593469 opened: [2.0] VMware power type error: __init__() takes 1 positional argument but 2 were given