=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
=== lazyWeekend is now known as lazyPower
=== jfarschman is now known as MilesDenver
[19:07] <tz__> I added a second interface on my cluster. When commissioning a new node, it correctly gets DHCP for the new subnet, but cloud-init gives the error: url_helper.py[WARNING]: Calling 'http://169.254.168.254/2009-04-04/meta-data/instance-id failed [x/y]:  url error [[Errno 113] No route to host]' .. Where is it getting this IP/route from and how can I force it to point to the correct maas server?
[19:15] <tz__> basically the same problem as the person who posted this: http://askubuntu.com/questions/486821/url-helper-py-warning-cannot-route-to-host-ubuntu-server
[19:32] <tz__> apparently the 169.254.169.254 url is a default for EC2 instances in cloud-init. any ideas on how to tell it (maas, cloud-init, metadata server) that its not EC2 and it should connect to maas?
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr
[21:40] <tz__> is there a fast way to login to a commisioned node (ie for the default ubuntu user) ? I'm trying to troubleshoot a cloud-init bug but cant login to look at the log files
[21:41] <jhobbs> tz__: https://maas.ubuntu.com/docs/troubleshooting.html
[21:41] <jhobbs> look at the Debugging ephemeral image section
[21:48] <tz__> interesting, that has one too many directory wildcards. taking it down to 5 fixes it though
[21:52] <jhobbs> ah, yeah, it's for 1.7
[21:55] <tz__> any suggestions on reading to make the commissioning script point to the maas metadata instead of EC2? I suspect that's what these cloud-init logs are going to say is happening
[21:57] <jhobbs> EC2 shouldn't be involved in commissioning or any other time - are you sure the nodes are getting DHCP? you can ssh into them while they're commissioning?
[21:58] <tz__> yes i can confirm they are getting the correct DHCP address. It's just booting up now so I'll see what the OS says when I login with the backdoor installed.
[22:00] <tz__> url_helper.py just retries for 120s trying to contact the 169.254.169.254 (EC2) address for some reason though, as if EC2 was set as the default on this additional interface
[22:04] <jhobbs> can you reach MAAS's metadata server from the node?
[22:05] <jhobbs> tz__: can you post your cloud-init.log in a pastebin
[22:05] <tz__> I can ping it, yes. It's just an additional virtual interface on the one maas controller
[22:05] <tz__> ls
[22:15] <tz__> http://pastebin.com/vFmfzWNY .. just reading through it now
[22:19] <jhobbs> tz__: don't see much of use in there, how about /var/log/cloud-init-output.log, /var/log/dmesg
[22:35] <tz__> jhobbs: http://pastebin.com/GT5EKyZn .. strange it's trying to hit a webserver on the..  gateway
[22:37] <jhobbs> tz__: what is MAAS's IP?
[22:39] <tz__> .16
[22:39] <jhobbs> tz__: can you post dmesg?
[22:40] <tz__> it has multiple vlan interfaces, 10.100.84.16, 10.100.98.16, etc
[22:46] <bigjools> morning