Restore fails with "getsockopt: connection timed out"

[Christopher Lee]

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

Error message:

06:25:59 ERROR juju.api.backups restore.go:81 could not clean up after failed backup upload: cannot complete restore: <nil>: Restore did not finish succesfuly
06:25:59 ERROR cmd supercommand.go:458 cannot upload backup file: PUT https://54.89.6.25:17070/model/60ff1a44-d81f-4423-8f18-b193327ef503/backups: Put https://54.89.6.25:17070/model/60ff1a44-d81f-4423-8f18-b193327ef503/backups: dial tcp 54.89.6.25:17070: getsockopt: connection timed out

[John A Meinel (jameinel)]

We should make sure that the restore-backup code that creates the controller is waiting for the controller to be up and ready. (like with 'juju bootstrap' waiting for a successful API call.)

If we are already waiting in the code, we can probably assume this bug is fixed, as we don't have a reproduction for it after 1year.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.