[14:02] <dimitern> rvba, blake_r, mpontillo, roaksoax, maas+juju net call?
[14:05] <kiko> dimitern, they are sprinting this week fwiw
[14:05] <rvba> Hi dimitern.
[14:07] <dimitern> kiko, rvba, hi
[14:07] <dimitern> ok, nothing new
[14:07] <dimitern> happy sprinting ;)
[21:03] <travnewmatic> hello all, got an enlistment question
[21:03] <travnewmatic> the first node that i'm trying to add to my maas cluster boots from pxe, ultimately ends up at an ubuntu login prompt, but my cluster controller has no knowledge of the node3
[21:03] <travnewmatic> of the node*
[21:05] <travnewmatic> http://pastebin.com/xQedSKqV
[21:26] <travnewmatic> http://pastebin.com/gXrMwwUF
[21:34] <roaksoax> travnewmatic: is the node in MAAS marked New ?
[21:34] <travnewmatic> the node does not show up anywhere in my maas interface
[21:34] <travnewmatic> but it did boot into an os over the network
[21:34] <travnewmatic> so the dhcp stuff is working
[21:34] <travnewmatic> and i can ping it
[21:35] <travnewmatic> but its like the region controller or the cluster controller have no knowledge of it
[21:38] <roaksoax> travnewmatic: so it needs to dhcpd from maas, then pxe, then you will see a prompt like maas-enlist
[21:38] <roaksoax> travnewmatic: and the node needs to do stuff inseide of itself to register itself in maas
[21:38] <travnewmatic> hmm
[21:39] <travnewmatic> well iknow dhcp is working
[21:39] <travnewmatic> and the pxe part is pushing an image to the server
[21:41] <travnewmatic> i see a table
[21:42] <travnewmatic> net device info
[21:42] <travnewmatic> route info
[21:42] <travnewmatic> and then it goes into some url_helper.py[WARNING] stuff
[21:42] <travnewmatic> errno 113 no route to host
[21:45] <travnewmatic> http://i.imgur.com/A5D5hXR.jpg
[21:46] <travnewmatic> then this http://i.imgur.com/RE4cHtm.jpg
[21:48] <travnewmatic> aaaaand then this http://i.imgur.com/6SqfzvD.jpg
[21:48] <travnewmatic> and if i hit enter the usual ubuntu login: pops up
[21:48] <roaksoax> travnewmatic: can your nodes contact 192.168.100.2 ?
[21:48] <roaksoax> travnewmatic: 192.168.100.2 is the address of the MAAS region server?
[21:49] <roaksoax> travnewmatic: it seems the nodes can't access it
[21:49] <travnewmatic> yes!
[21:49] <travnewmatic> hmm :|
[21:49] <travnewmatic> alright
[21:49] <travnewmatic> subnet issue?
[21:50] <roaksoax> travnewmatic: that might be it. can you ensure your nodes would be able to ping the maas server?
[21:50] <travnewmatic> lemme check
[21:50] <roaksoax> travnewmatic: is the DHCP range configured in maas in the same network, and can actually ping?
[21:50] <travnewmatic> well
[21:50] <travnewmatic> as it is now
[21:50] <travnewmatic> i only have one node
[21:50] <travnewmatic> and that node is presenting me with a login prompt
[21:50] <travnewmatic> and i'm not sure what the un/pw is
[21:51] <travnewmatic> also
[21:51] <travnewmatic> i first setup the region controller
[21:51] <travnewmatic> then i setup the cluster controller
[21:51] <roaksoax> travnewmatic: that's fin
[21:51] <roaksoax> travnewmatic: let the user auto register itself in maas, and you will see it appear there
[21:52] <travnewmatic> hmm
[21:52] <travnewmatic> well i ran the dkpg configure cluster controller command thing
[21:52] <travnewmatic> put in the api address of the region controller
[21:52] <travnewmatic> and added the second maas controller to the first
[21:53] <travnewmatic> so the first maas controller, the 192.168.0.2 machine, lists 2 clusters
[21:53] <travnewmatic> on the region controller, i went into that added cluster controller and added a managed interface, with dhcp and dns
[21:54] <travnewmatic> the cluster controllers address is 192.168.0.3
[21:54] <travnewmatic> when i go to  192.168.0.3/MAAS
[21:54] <travnewmatic> its like everything is fresh
[21:54] <travnewmatic> i dont see that managed interface that i created
[21:55] <travnewmatic> although it does exist on the  192.168.0.2 interface for the  192.168.0.3 cluster controller
[21:55] <roaksoax> travnewmatic: that's because you don't need to install the Region controller on the Cluster controller
[21:55] <travnewmatic> aaaaaah okay
[21:55] <roaksoax> travnewmatic: when you install sudo apt-get install maas , it will install both Region (maas-reiogn-controller) and Cluster (maas-cluster-controller)
[21:55] <travnewmatic> uhuh
[21:56] <roaksoax> travnewmatic: if you want to add *another* cluster controller, which is not running on the same machine of the region, you only have to install maas-cluster-controller, and then dpkg-reconfigure maas-cluster-controller to point it to the *region* controller
[21:56] <travnewmatic> mmm i see
[21:57] <travnewmatic> when i did the cluster controller, i did it from the ubuntu server install media maas option
[21:57] <roaksoax> travnewmatic: so the base installation (sudo apt-get install maas) should allow you to control your maas and configure the *default* cluster (the one runnin with the region)
[21:57] <travnewmatic> mhm
[21:57] <roaksoax> travnewmatic: and if you have nodes that can talk ot the maas server, you just need to allow them to PXE boot and that's it
[21:58] <travnewmatic> so the cluster controllers act as intermediaries between nodes and the region controller
[21:59] <roaksoax> travnewmatic: correct
[21:59] <travnewmatic> hmm
[22:00] <travnewmatic> https://www.dropbox.com/s/bjhn5qrs3ma02rf/Screenshot%202015-02-17%2015.59.38.png?dl=0
[22:00] <travnewmatic> so if i wanted to put everything on the same subnet
[22:01] <travnewmatic> i think right now i'm using 192.168.0.1 through 192.168.0.4
[22:02] <travnewmatic> what is the router ip?
[22:03] <roaksoax> travnewmatic: depends whether you hvae a default gw, or maas is your default gw
[22:03] <travnewmatic> i've got a box doing nat
[22:04] <travnewmatic> so 192.168.0.1 is what i've got everything point to for their gateway
[22:06] <roaksoax> travnewmatic: say, your router is 192.168.0.1, your maas server 192.168.0.2. When you configure your dynamic range, it will use 0.4 to 0.14, and static range from 0.15 to 0.25
[22:06] <roaksoax> travnewmatic: so router address is 192.168.0.1
[22:06] <travnewmatic> mhm
[22:06] <catbus1> looks like he has 1.5 there. not 1.7.
[22:07] <catbus1> maas I mean.
[22:07] <roaksoax> travnewmatic: ah, so if there's just 1 range, then you only need 1 range
[22:07] <travnewmatic> i'm putting everything on 192.168.0.0
[22:10] <travnewmatic> http://pastebin.com/0nRnmUpH
[22:11] <travnewmatic> https://www.dropbox.com/s/duoi6f19nt8vlw5/Screenshot%202015-02-17%2016.10.59.png?dl=0
[22:12] <travnewmatic> aaand now dhcp and pxe is borked :D
[22:16] <travnewmatic> restarting my cluster controller
[22:16] <travnewmatic> the cluster controller has the only managed interface
[22:19] <travnewmatic> i forgot to change the network in the network tab in the maas interface
[22:19] <travnewmatic> might that have had something to do with it?
[22:21] <catbus1> dpkg-reconfigure maas-cluster-controller didn't help to get dhcp back?
[22:23] <travnewmatic> yaaay pxe works again
[22:23] <travnewmatic> i think
[22:23] <travnewmatic> hmm
[22:23] <travnewmatic> now its just sitting there
[22:23] <travnewmatic> TFTP.
[22:23] <travnewmatic> gateway ip is 192.168.0.1
[22:24] <travnewmatic> http://imgur.com/2vQfpf7
[22:25] <travnewmatic> hanging on the tftp thing
[22:26] <travnewmatic> HNNNG it should be .2
[22:26] <travnewmatic> hold on
[22:26] <travnewmatic> should it?
[22:27] <travnewmatic> my gateway to my nat box is .1
[22:27] <travnewmatic> region controller is .2
[22:27] <travnewmatic> cluster controller is .3
[22:27] <travnewmatic> and the interface with dhcp is .4
[22:28] <catbus1> You set the router IP to 192.168.0.1. It should be .1.
[22:28] <travnewmatic> so thats right?
[22:29] <travnewmatic> yeah its still hangin on the tftp thing
[22:29] <catbus1> That's right, it's getting IP address from the dhcp server which you set to .4. But I *think* the node needs to reach cluster controller to get the image files.
[22:29] <travnewmatic> but it is getting an address from dhcp
[22:29] <travnewmatic> hmm
[22:30] <catbus1> could you set eth1 internface as unmanaged on maas web ui, and set eth0 interface to manage dhcp and dns with the same settings, except IP would be 192.168.0.3 not 192.168.0.4.
[22:30] <travnewmatic> this is odd i was getting farther with having stuff on a separate subnet
[22:30] <travnewmatic> hmm alright i can try that
[22:31] <travnewmatic> so i'll ditch eth1
[22:32] <travnewmatic> https://www.dropbox.com/s/026yyfjix0h5zpr/Screenshot%202015-02-17%2016.32.13.png?dl=0
[22:32] <travnewmatic> didnt ditch it just set it to unmanaged
[22:32] <catbus1> that looks good.
[22:32] <travnewmatic> and moved the config stuff to eth0
[22:33] <catbus1> config stuff?
[22:33] <travnewmatic> i mean
[22:33] <travnewmatic> the dhcp and dns form stuff
[22:33] <travnewmatic> router ip , high, low, etc
[22:33] <catbus1> right.
[22:33] <travnewmatic> aaaaaand we're on our way
[22:33] <travnewmatic> pxe pushing stuff over as it should
[22:35] <travnewmatic> maas-enlisting-node login!
[22:35] <travnewmatic> wow thanks guys this is really flipping sweet
[22:35] <catbus1> great. does the node show up on the nodes page on maas web ui now? as New.
[22:36] <travnewmatic> mmm
[22:36] <travnewmatic> does not :(
[22:36] <catbus1> or Declared
[22:36] <catbus1> the node should power off, after that it will show up on the web UI.
[22:37] <travnewmatic> erhmahgerd thats exactly what it did
[22:38] <travnewmatic> https://www.dropbox.com/s/8v58n0ppiswxhoa/Screenshot%202015-02-17%2016.37.28.png?dl=0
[22:38] <travnewmatic> https://www.dropbox.com/s/q33bvk4nz7s5wgx/Screenshot%202015-02-17%2016.38.00.png?dl=0
[22:38] <catbus1> great. now you can commission the node, so MAAS knows how many CPU cores and RAM it has.
[22:39] <travnewmatic> i'm not sure it knows how to power it back on
[22:39] <catbus1> Click Edit node on the node page.
[22:40] <catbus1> MAAS should have created IPMI credentials to power control the node.
[22:42] <travnewmatic> did not :(
[22:42] <travnewmatic> manually powering it back on
[22:43] <catbus1> could you show the screen shot of the node details page (click Edit node).
[22:43] <travnewmatic> unmomento
[22:45] <travnewmatic> https://www.dropbox.com/s/10b8tv3izrs9jmp/Screenshot%202015-02-17%2016.44.55.png?dl=0
[22:46] <catbus1> It says the cluster controller for this node is not responding, power type validation is not available.
[22:47] <travnewmatic> :(
[22:47] <catbus1> do you mind doing dpkg-reconfigure maas-cluster-controller again to make sure you tell the cluster controller where region controller is?
[22:48] <travnewmatic> after the restart https://www.dropbox.com/s/ids7cnfcm1jntu7/Screenshot%202015-02-17%2016.47.40.png?dl=0
[22:49] <travnewmatic> done
[22:49] <catbus1> If it's all working as it should, you should not need to power on/off the node manually, MAAS should take care of that for you.
[22:50] <catbus1> MAAS region controller API URL should be http://192.168.0.2/MAAS for the cluster controller configuration.
[22:50] <travnewmatic> yep thats exactly what i put
[22:51] <catbus1> you mentioned you had two cluster controllers.
[22:51] <travnewmatic> no, a region and a cluster
[22:51] <catbus1> ok.
[22:52] <catbus1> i don't remember exactly how maas 1.5 should show the power control info on the node page.
[22:53] <travnewmatic> well
[22:54] <travnewmatic> thres a dropdown in the edit page "power type"
[22:54] <catbus1> MAAS should have it filled up automatically after the enlistment.
[22:55] <catbus1> i don't know what log files to look at in /var/log/maas/ to find out what's going on.
[22:56] <travnewmatic> ERROR 2015-02-17 16:54:46,136 maasserver Unable to get RPC connection for cluster 'maas'
[22:56] <travnewmatic> might this be it?
[22:57] <catbus1> https://bugs.launchpad.net/maas/+bug/1350925
[22:58] <travnewmatic> poop
[23:00] <catbus1> could be DNS hostname resolve issue
[23:01] <travnewmatic> hmmmm
[23:01] <travnewmatic> or an ssh key issue
[23:07] <catbus1> does putting hostname in the /etc/hosts file help?
[23:07] <j^2> if anyone uses chef here, i just pushed up: https://rubygems.org/gems/knife-maas
[23:08] <j^2> it would be awesome if yall could give it a shot and report any bugs to the issues page
[23:08] <travnewmatic> catbus1, on the region controller?
[23:14] <travnewmatic> yeah i tried it on another 1950 and it doesnt like the ipmi
[23:15] <travnewmatic> i see that thread though
[23:15] <travnewmatic> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1321885
[23:17] <catbus1> travnewmatic: I am not sure actually. I have never deployed region and cluster on different nodes. Region couldn't contact cluster, and it could be name resolving issue, cluster is providing DNS service, so region should reach to cluster for DNS service. I would try this, edit /etc/resolv.conf and have cluster controller IP as the first nameserver entry, and see if it works.
[23:17] <travnewmatic> well
[23:17] <travnewmatic> i could try cutting out the cluster controller
[23:18] <travnewmatic> does this not appear to be an issue with the ipmi in the 1950?
[23:18] <travnewmatic> my error does seem to match what is described in that bug
[23:18] <catbus1> it could be related to hardware. yes.
[23:21] <catbus1> travnewmatic: you can find your maas version with apt-cache policy maas
[23:21] <travnewmatic> 1.5
[23:22] <catbus1> fix verified with 1.7
[23:23] <travnewmatic> so i should upgrade
[23:24] <catbus1> travnewmatic: you can get 1.7.1 from maas-maintainers/stable ppa, sudo add-apt-repository ppa:maas-maintainers/stable
[23:25] <travnewmatic> gotcha
[23:25] <catbus1> sudo apt update and sudo apt install maas
[23:27] <catbus1> choose to use the new configuration template during the install maas process. after it's upgraded to 1.7, you need to re-import the image files and there is a new IP range (Dynamic and Static) in the network interface you will need to configure.
[23:28] <travnewmatic> hmm i see
[23:30] <travnewmatic> both region and cluster are upgrading
[23:30] <travnewmatic>  Y or I  : install the package maintainer's version
[23:31] <travnewmatic> this is what you're referring to?
[23:31] <catbus1> yes.
[23:31] <travnewmatic> gotcha
[23:32] <travnewmatic> i really appreciate all the help this afternoon
[23:40] <travnewmatic> shit you guys are awesome https://www.dropbox.com/s/0rq88uhv6872tcb/Screenshot%202015-02-17%2017.39.57.png?dl=0
[23:41] <travnewmatic> i was wondering why some of the screenshots in some of the guides looks a tad different than what i was seeing on my screen
[23:42] <travnewmatic> wow it seems like this update adds a lot
[23:49] <travnewmatic> also it appears that my cluster controller has been disconnected from my region controller after the upgrade
[23:49] <j^2> travnewmatic: yeah 1.7.1+ is the way to go
[23:50] <j^2> most of the docs are 1.5
[23:50] <travnewmatic> ive noticed
[23:52] <travnewmatic> hopefully the documentation will catch up soon
[23:56] <travnewmatic> where does juju get installed?  on the region controller?