Comment 4 for bug 1214181

I found that when I use
    public-storage-account-name: jujutools
    public-storage-container-name: juju-tools
in my environment.yaml I cannot deploy a service. Juju is unable to make a connection to the Mongo DB state server:

2013-08-20 04:41:20 INFO juju open.go:69 state: opening state; mongo addresses: ["juju-azure-39kx9e7p2d.cloudapp.net:37017"]; entity ""
2013-08-20 04:41:20 ERROR juju open.go:89 state: connection failed, will retry: dial tcp 137.135.9.24:37017: connection refused
2013-08-20 04:41:20 ERROR juju open.go:89 state: connection failed, will retry: dial tcp 137.135.9.24:37017: connection refused
. . . 10 minutes later . . .
2013-08-20 04:51:21 ERROR juju supercommand.go:282 command failed: no reachable servers

If I comment out
    public-storage-account-name: jujutools
    public-storage-container-name: juju-tools
in my environment .yaml I see:
http://pastebin.ubuntu.com/6005300/
  -basically 1.12 tools uploaded and used

Although I get
2013-08-20 05:03:16 INFO juju open.go:69 state: opening state; mongo addresses: ["juju-azure-t4s3mf6fm6.cloudapp.net:37017"]; entity ""
2013-08-20 05:04:19 ERROR juju open.go:89 state: connection failed, will retry: dial tcp 138.91.157.184:37017: connection timed out
. . . 8 minutes later . . .
I do see
2013-08-20 05:11:24 INFO juju open.go:107 state: connection established

Not sure why adding in a public-storage-* causes this issue. Note juju-tools has 1.13.0 and 1.13.1 amd64 juju public tools, and I am using a 1.13.2 Juju client.