[00:01] <f1gjam> ok ill ask there
[00:43] <mpontillo> bdx: looks great; glad MAAS is working well for you =)
[00:48] <f1gjam> hey guys i tried #ubuntu-solutions - no joy
[00:48] <f1gjam> also trying in ubuntu-server
[00:55] <mpontillo> f1gjam: the traceback is saying juju tried to deploy a MAAS node but it failed to change state to "Deployed". Can you try using MAAS to deploy a node manually and see if it works? Which version of MAAS did you install?
[01:22] <f1gjam> Maas version 1.9
[01:23] <f1gjam> MAAS Version 1.9.3+bzr4577-0ubuntu1 (trusty1)
[01:23] <f1gjam> going to deploy OS now
[01:28] <f1gjam> so the machine looks like its done
[01:28] <f1gjam> but MaaS is saying deploying still
[01:30] <f1gjam> is there a log i can follow to see what MaaS is waiting on?
[01:36] <mpontillo> f1gjam: hmm, that may indicate a lack of connectivity to the MAAS server from the deployed node
[01:37] <mpontillo> f1gjam: is there an installation log on the node details page? (it would be in the drop-down box alongside the commissioning results and summary)
[01:38] <mpontillo> f1gjam: are you able to SSH to the machine and check the cloud-init logs?
[01:39] <f1gjam> ok
[01:39] <f1gjam> so its finsihed but still saying deploying
[01:40] <f1gjam> do you want commissioning oupiut
[01:46] <bdx> sure would be cool if dns was modifiable from the gui .....
[01:47] <bdx> i guess it wouldn't really make sense though
[01:49] <bdx> pushing for container hostname specification capibility ... I guess that would be on the juju side of things though eh?
[01:49] <f1gjam> ok i am going to sleep - will try again in the morning
[01:50] <bdx> f1gjam: yea, the more logs the better
[01:50] <bdx> you can easily get them shareable with the tool 'pastebinit'
[01:51] <bdx> flgjam: e.g. `cat /var/log/apache2/error.log | pastebinit`
[01:52] <bdx> flgjam: would return a url with your log
[01:52] <bdx> flgjam: you should try to compile a list of logs, and paste them on #ubuntu-solutions
[01:53] <bdx> flgjam: if no one is around, they will answer you when they come back
[01:54] <mpontillo> f1gjam: if there is commissioning output, that's good, but I was more interested in if there was an install log
[06:33] <wililupy> Using MAAS 2.0 with an external DHCP server, I keep running into deployment issues. The servers start up, they get an IP, but when they try to go online to setup, they try an APIPA address and then default back to my gateway's IP address, but never successfully commision. Anyone else expirience this?
[06:34] <wililupy> If I have MAAS act as DHCP/DNS server, I can commission, but I don't want to have to create a seperate routeable network segment if I don't have to.
[12:04] <f1gjam> hey mpontillo - Are you around. The installation of the OS failed. There isnt an install available either.
[14:32] <f1gjam> this is all i get:  [ERROR] OS-LEN1: Marking node failed: Node operation 'Deploying' timed out after 0:40:00.
[16:27] <f1gjam> is there a proper up to date guide which tells you how to setup MaaS step by step?
[18:01] <mpontillo> f1gjam: the docs linked off of http://maas.io/ should be relatively up to date.  can you take a look at the system console during the deployment to see if there are any errors? is there an installation log available in the node details page?
[18:01] <mpontillo> f1gjam: you might also check /var/log/maas/rsyslog/<node> for clues
[18:02]  * mpontillo won't be watching IRC closely, as it's the weekend, just so you know
[18:03] <f1gjam> hey mpontillo
[18:03] <f1gjam> ok going to check now
[18:03] <f1gjam> let me re-provision
[18:03] <f1gjam> since i released all the nodes
[18:04] <f1gjam> mpontillo, appreciate any help however slow it is :)
[18:04] <f1gjam> one question
[18:04] <f1gjam> do i need to do any iptables configuration
[18:05] <f1gjam> my networks are - 192.168.10.0/24 (External) - 192.168.20.0/24 (Internal)
[18:06] <f1gjam> when i look at the system being provisioned it seems to provision all the way.... albeit i cant logon ...
[18:21] <mpontillo> f1gjam: well, the deployed node must be able to access the MAAS server (to fetch SSH keys and send the indication that the node is now "Deployed"). Not sure about iptables; depends on your setup, but you'll want to verify that if a host is configured on that network it is able to reach MAAS
[18:22] <f1gjam> its installed
[18:22] <f1gjam> currenlty at
[18:22] <f1gjam> Source MaaS http://192.168.10.1/MAAS/metadata/curtin
[18:22] <mpontillo> f1gjam: often times if there is a firewall or NAT involved and the deployed node cannot reach MAAS, what you need to do is "sudo dpkg-reconfigure -plow maas-rack-controller" and make sure the URL to the MAAS region is set to one that will be able to be reached from the network the nodes are deployed on
[18:22] <f1gjam> rsyslog is empty
[18:23] <f1gjam> ok - so my network setup is as follows:
[18:23] <mpontillo> f1gjam: so what I would do is make sure that the 192.168.20.x IP address is being used for the MAAS URL. it's possible that the deployment network cannot reach the "external" IP you are using for the MAAS region?
[18:23] <f1gjam> 192.168.10.0/24 - MAAS IP 192.168.10.1 / GATEWAY = 192.168.10.254 (REAL FIREWALL/ROUTER) -This is my external network
[18:24] <f1gjam> 192.168.20.0/24 - MAAS given adress of  192.168.20.1 on interface eth1
[18:24] <mpontillo> f1gjam: also make sure that all the proper subnet gateways are configured in MAAS (check the details page for each subnet under "Networks" in MAAS)
[18:24] <f1gjam> thats one quesion
[18:24] <f1gjam> so lets say external network 192.168.10.1
[18:25] <f1gjam> has the correct gatwway etc...
[18:25] <f1gjam> but in 192.168.20.1
[18:25] <mpontillo> f1gjam: okay, and how are the deployed nodes expected to get off-subnet? what is their router supposed to be? the MAAS server?
[18:25] <f1gjam> MAAS
[18:25] <f1gjam> 192.168.20.1
[18:25] <mpontillo> f1gjam: okay then yes you'll need to ensure routing is enabled on the MAAS server and whatever iptables rules necessary are in place
[18:26] <f1gjam> why?
[18:26] <mpontillo> f1gjam: my guess is that the deployed nodes are trying to hit MAAS on the external IP address and it isn't working due to routing issues
[18:26] <f1gjam> I mean the document statues to set
[18:27] <mpontillo> f1gjam: alternatively you can do the dpkg-reconfigure command I suggested earlier to make sure the deployed nodes hit MAAS on the internal network interface
[18:27] <f1gjam> and change the MaaS IP?
[18:27] <f1gjam> to the internal address?
[18:27] <mpontillo> f1gjam: yes
[18:28] <f1gjam> https://screencloud.net/v/lVjd
[18:29] <f1gjam> https://screencloud.net/v/xzDb
[18:31] <f1gjam> https://screencloud.net/v/377
[18:37] <f1gjam> brb
[18:40] <f1gjam> if i change the router ip to the REAL router for the .20 netowkr
[18:40] <f1gjam> i get
[18:40] <f1gjam> calling 192.168.20.254//latest/meta--data/instance-id sp im guessing it has to be the address of the MaaS server
[19:04] <mpontillo> f1gjam: ah, you are on MAAS 1.9? for some reason I was assuming you were on 2.0
[19:05] <mpontillo> f1gjam: some of my instructions were wrong then. "sudo dpkg-reconfigure -plow maas-cluster-controller" (not rack-controller)
[19:06] <mpontillo> f1gjam: did you send a screenshot of the configuration of the eth0 interface?
[19:07] <mpontillo> f1gjam: there is no requirement that the router IP is the MAAS server. you can define the router IP on the cluster interface settings page
[19:30] <f1gjam> im back sorry was afk
[19:30] <f1gjam> the problem is
[19:30] <f1gjam> if i set the GW IP of eth0 which is the private interface to 192.168.20.254
[19:30] <f1gjam> it those that error about
[19:33] <f1gjam> https://screencloud.net/v/3m9g <-- eth0 configuration (private network)
[19:44] <f1gjam> https://screencloud.net/v/64N
[19:44] <f1gjam> if i put the gateway as
[19:44] <f1gjam> 192.168.20.254
[19:44] <f1gjam> I get that issue
[20:15] <mpontillo> f1gjam: oh, that's interesting. are you redirecting MAAS to an SSL-enabled site?
[20:17] <mpontillo> f1gjam: I would try running "dpkg-reconfigure -plow maas-cluster-controller" and make sure the MAAS URL is set to http://192.168.20.1:5240/MAAS/
[20:17] <mpontillo> f1gjam: that way you'll ensure you are talking directly to MAAS without any thing in between
[20:18] <f1gjam> ok
[20:18] <f1gjam> but..
[20:18] <f1gjam> if you look from that pick thats when i point it to the router as the default GW for the 192.168.20.x network
[20:18] <f1gjam> that issue doesnt come up
[20:18] <f1gjam> if i make the gateway 192.168.20.1 = MAAS
[20:42] <mpontillo> f1gjam: yeah, that is weird and I can't explain that right now (though I've seen it in the past, I wonder if it's some kind of a fallback); I'm pretty sure it should be using the MAAS URL configured on the cluster, not the gateway, to attempt to contact the cloud-init data source
[21:22] <f1gjam> mpontillo, sorry i disconnected
[21:22] <f1gjam> back now
[22:23] <f1gjam> https://screencloud.net/v/QUf
[23:30] <boxo> Hello
[23:31] <boxo> i ned more info for mass