Restore fails with "getsockopt: connection timed out"
Bug #1632148 reported by
Christopher Lee
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Eric Claude Jones |
Bug Description
As seen here: http://
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:/
Changed in juju: | |
status: | Confirmed → Triaged |
Changed in juju: | |
assignee: | nobody → Eric Claude Jones (ecjones) |
tags: | added: backup-restore |
tags: | removed: restore-backup |
To post a comment you must log in.
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.