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