restore-backup never completes
Bug #1576874 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Critical
|
Horacio Durán | ||
Bug Description
As seen in
http://
http://
restore-backup does complete. We see a timeout.
| tags: | added: blocker |
| Changed in juju-core: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju-core: | |
| assignee: | Ian Booth (wallyworld) → Horacio Durán (hduran-8) |
| Changed in juju-core: | |
| milestone: | 2.0-beta7 → 2.0-beta8 |
| tags: | removed: blocker |
| tags: | added: blocker |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 2.0-beta8 → 2.0-beta9 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta9 → none |
| milestone: | none → 2.0-beta9 |
To post a comment you must log in.
The are several issues here. The restore command was swallowing errors, and the server side logs were being replaced with those from the backup, and the deletion of the log file prevented new logs from being saved, as well as hiding the logs from the first stage of the restore. These issues combined pointed to a different root cause. Once fixed, the real issues are:
- backups don't contain the systemd service configs
- restoredump is fundamentally different in 3.2 vs 2.4
All issues except the last have been fixed in a WIP branch. Getting restore working with 3.2, and remaining backwards compatible with 2.4, is a non-trivial amount of work. It should be possible to leverage the work done previously for the upgrade mongo command.