juju times out after 10 minutes when bootstrapping which makes bootstrapping on slow connections impossible

[Jeff Lane ]

ubuntu@CloudOne:~$ juju bootstrap --upload-tools -v
verbose is deprecated with the current meaning, use show-log
2014-01-29 10:35:25 INFO juju.environs open.go:156 environment info already exists; using New not Prepare
2014-01-29 10:35:26 INFO juju.environs.tools build.go:162 found existing jujud
2014-01-29 10:35:26 INFO juju.environs.tools build.go:172 target: /tmp/juju-tools064938138/jujud
2014-01-29 10:35:29 INFO juju.environs.sync sync.go:230 built 1.17.0.1-trusty-amd64 (6562kB)
2014-01-29 10:35:29 INFO juju.environs.sync sync.go:71 listing available tools
2014-01-29 10:35:29 INFO juju.environs.sync sync.go:95 found 2 tools
2014-01-29 10:35:29 INFO juju.environs.sync sync.go:105 listing target bucket
2014-01-29 10:35:32 INFO juju.environs.sync sync.go:118 found 2 tools in target; 0 tools to be copied
2014-01-29 10:35:32 INFO juju.environs.sync sync.go:123 copied 0 tools
2014-01-29 10:35:32 INFO juju.environs.sync sync.go:125 generating tools metadata
2014-01-29 10:35:35 INFO juju.environs.tools simplestreams.go:357 Writing tools/streams/v1/index.json
2014-01-29 10:35:36 INFO juju.environs.tools simplestreams.go:357 Writing tools/streams/v1/com.ubuntu.juju:released:tools.json
2014-01-29 10:35:36 INFO juju.environs.sync sync.go:137 tools metadata written
2014-01-29 10:35:37 INFO juju.environs.bootstrap bootstrap.go:46 bootstrapping environment "maas"
2014-01-29 10:35:37 INFO juju.environs.tools tools.go:85 reading tools with major.minor version 1.17
2014-01-29 10:35:37 INFO juju.environs.tools tools.go:93 filtering tools by version: 1.17.0.1
2014-01-29 10:35:37 INFO juju.environs.tools tools.go:96 filtering tools by series: precise
2014-01-29 10:35:39 INFO juju.environs.bootstrap bootstrap.go:58 picked newest version: 1.17.0.1
Launching instance
2014-01-29 10:35:39 WARNING juju.provider.maas environ.go:193 picked arbitrary tools &{"1.17.0.1-precise-amd64" "http://10.0.0.1/MAAS/api/1.0/files/?key=cef059a6-88c8-11e3-9210-eca86bfd11f4&op=get_by_key" "6e7578b0bb530f407bf4269c20210b7b48a2f117fe6f89a5ed842e3ab1d7c082" %!q(int64=6719611)}
 - /MAAS/api/1.0/nodes/node-db10f41c-83ae-11e3-bd54-eca86bfd11f4/
Waiting for address
Attempting to connect to Slave6.master:22
Attempting to connect to 10.0.0.15:22
2014-01-29 10:45:40 ERROR juju.provider.common bootstrap.go:85 bootstrap failed: waited for 10m0s without being able to connect: ssh: connect to host 10.0.0.15 port 22: Connection refused
Stopping instance...
2014-01-29 10:45:40 ERROR juju.cmd supercommand.go:294 waited for 10m0s without being able to connect: ssh: connect to host 10.0.0.15 port 22: Connection refused

I've now run into this in two locations, one in a classroom where we were attempting to learn/use MAAS and Juju and failed to actually do useful hands-on work because juju would time out at 10 minutes, which was way to fast for our classroom internet connection.

Also with the sprint in london while we were trying to get MAAS and Juju working offline. Even using closely connected machines there were MANY occasions where bootstrapping using d-i would take longer than 10 minutes thus making it impossible to bootstrap. We were unable to use fast path for other reasons in this case.

Finally, there are plenty of servers in the real world that will take 10 Minutes or more to POST so throw in the time to install either via fast-path or d-i and you could easily have a fleet of systems in a real-world deployment scenario that fail to reply because of this arbitrary 10 minute timeout.

The timeout should be configurable somehow, in the juju-gui via an option perhaps globally or per charm when installing, in the juju cli via a switch or via maas passed to juju.