Cannot assign unit: unable to connect

[Aaron Bentley]

Juju add-unit fails with e.g. cannot assign unit "dummy-source/3" to machine: ... Unable to connect to: 10.0.8.1:8443

As seen here:
http://reports.vapour.ws/releases/issue/57b718bd749a56656cd89abf

This appears to be intermittent, because the previous attempt got further.

Full add-unit output:
2016-08-19 02:54:39 INFO juju --debug add-unit -m functional-scale-out:functional-scale-out dummy-source -n 5
02:54:39 INFO juju.cmd supercommand.go:63 running juju [2.0-beta16 gc go1.6.2]
02:54:39 INFO juju.juju api.go:74 connecting to API addresses: [[fdb0:d78:ed75:9824:216:3eff:fe9e:3d9a]:17070 10.0.8.139:17070]
02:54:39 INFO juju.api apiclient.go:518 dialing "wss://[fdb0:d78:ed75:9824:216:3eff:fe9e:3d9a]:17070/model/e1e29698-4b55-4de8-8dea-b304dc4f1a78/api"
02:54:39 INFO juju.api apiclient.go:313 connection established to "wss://[fdb0:d78:ed75:9824:216:3eff:fe9e:3d9a]:17070/model/e1e29698-4b55-4de8-8dea-b304dc4f1a78/api"
02:54:39 DEBUG juju.juju api.go:248 API hostnames unchanged - not resolving
02:55:47 DEBUG juju.api apiclient.go:569 health ping failed: connection is shut down
02:55:47 ERROR cmd supercommand.go:458 cannot assign unit "dummy-source/3" to machine: cannot assign unit "dummy-source/3" to new machine or container: cannot assign unit "dummy-source/3" to new machine: Get https://10.0.8.1:8443/1.0: Unable to connect to: 10.0.8.1:8443
02:55:47 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/api/apiclient.go:628: } {github.com/juju/retry/retry.go:187: } {github.com/juju/juju/rpc/client.go:149: } {cannot assign unit "dummy-source/3" to machine: cannot assign unit "dummy-source/3" to new machine or container: cannot assign unit "dummy-source/3" to new machine: Get https://10.0.8.1:8443/1.0: Unable to connect to: 10.0.8.1:8443}])
2016-08-19 02:55:47 ERROR Command '('juju', '--debug', 'add-unit', '-m', 'functional-scale-out:functional-scale-out', 'dummy-source', '-n', '5')' returned non-zero exit status 1

[Anastasia (anastasia-macmood)]

This is a very old report and I can no longer reproduce this. My guess is that the intermittent failure was addressed as part of the work that we have done since this bug was filed.