[19:39] <Tug_> Hi, I'm trying to bootstrap a manual env but it fails to configure Juju machine agent
[19:39] <Tug_> this is the output I get: http://pastebin.com/tZ2sQErt
[19:39] <Tug_> any idea ?
[19:41] <Tug_> juju 1.20.13-trusty-amd64
[19:42] <Tug_> destination is a trusty vm as well
[22:05] <Tug_> now I have bootstraped the env but running juju status fails
[22:05] <Tug_> 2014-11-30 20:50:41 DEBUG juju.state.api apiclient.go:248 error dialing "wss://juju:17070/", will retry: websocket.Dial wss://juju:17070/: dial tcp 130.211.X.X:17070: connection refused
[22:18] <thumper> that url looks wrong
[22:18] <thumper> Tug_: bootstrapped what type of environment... with what config?
[22:19] <Tug_> thumper, manual env with very simple config
[22:19] <Tug_> bootstrap-host: juju
[22:19] <Tug_> the rest is default
[22:20] <thumper> hmm...
[22:20] <thumper> is the "juju" host the same as the machine you are running on?
[22:20] <thumper> or a different one?
[22:20] <Tug_> a different one
[22:20] <Tug_> actually I just tried something interesting
[22:21] <thumper> is it actually running?
[22:21] <Tug_> I installed juju-core on the machine agent
[22:21] <Tug_> and set up the same config and it worked
[22:21] <thumper> it shouldn't need that
[22:21] <thumper> so something looks wrong
[22:22] <Tug_> it looks like the port is closed maybe ?
[22:22] <thumper> can you uninstall juju-core and look again?
[22:22] <Tug_> on my machine ?
[22:22] <thumper> you can ssh to the machine and look in /etc/init to see if the jobs are registered
[22:22] <thumper> no, the fact that it failed before, then you installed juju-core on the other machine then it worked
[22:22] <thumper> could be a missing dependency
[22:22] <thumper> what version ?
[22:23] <Tug_> I mean it worked when I run juju status from the machine agent
[22:23] <Tug_> not from my machine
[22:23] <Tug_> 1.20.13-trusty-amd64
[22:24] <thumper> oh
[22:24] <thumper> perhaps it is just a problem resolving 'juju' ?
[22:24] <Tug_> I still get "connection refused" from my machine
[22:25] <Tug_> yeah that's what I was thinking
[22:25] <thumper> you can try this...
[22:25] <Tug_> but it does resolve to 130.211.X.X
[22:25] <thumper> it is a hack mind
[22:25] <Tug_> which is correct
[22:25] <Tug_> and then the port is open
[22:25] <Tug_> I think
[22:26] <thumper> well if it works on that machine, but not from your client
[22:26] <thumper> I'd double check that the port is open
[22:26] <thumper> can you telnet to it?
[22:26] <Tug_> telnet: Unable to connect to remote host: Connection refused
[22:26] <Tug_> nop
[22:27] <thumper> check your settings :-)
[22:27] <Tug_> yeah it must be that :)
[22:27] <Tug_> but sadly it's all set
[22:28] <Tug_> (it's just a network config on google compute engine)
[22:28] <Tug_> http://ifjfij.appspot.com/i?b=fe584c4a904d35cc52a5d807a46f6d3413f27308
[22:29]  * thumper shrugs
[22:39] <Tug_> at least I excluded juju from the cause :)
[22:40] <thumper> yeah, there is that
[22:47] <Tug_> or it could be... here is what I have with netstat
[22:48] <Tug_> tcp6       0      0 :::17070                :::*                    LISTEN      17596/jujud
[22:48] <Tug_> maybe juju does not forward ipv4 connections
[22:58] <Tug_> fyi, it was a bug in google cloud (for real) removing the rule and recreating it did the trick :)