backups restore: fails when machine number differs

Bug #1493458 reported by Nick Veitch
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
High
Unassigned

Bug Description

I get repeated failures trying to restore an HA environment

juju backups restore --id=<...>
ERROR could not exit restoring status: cannot complete restore: <nil>: Restore did not finish succesfuly
ERROR cannot perform restore: <nil>: restore failed: cannot load agent config from disk: cannot read agent config "/var/lib/juju/agents/machine-0/agent.conf": open /var/lib/juju/agents/machine-0/agent.conf: no such file or directory

Machine-0 is the new bootstrap instance created when restoring.
The machine-0 stuff doesn't exist - my backup file contains 'machine-6/agent.conf', as I guess that was the leader of the HA environment when I backed up. As the restore process seems to replace '/var/lib/juju/agents/*', it isn't possible to simply rename the file.

Also,the error message misspells 'successfully'.

tags: added: docteam
Revision history for this message
Nick Veitch (evilnick) wrote :

for clarification, this was running 1.24.5-trusty-amd64

Curtis Hovey (sinzui)
tags: added: backup-restore ha
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.25.1
tags: added: docteam-blocking
Changed in juju-core:
milestone: 1.25.1 → 1.26.0
Changed in juju-core:
milestone: 1.26.0 → 2.0-beta5
Changed in juju-core:
milestone: 2.0-beta5 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.1.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

This may have been fixed as part of other work. Please confirm that it still exists \o/

affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
Changed in juju:
status: Triaged → Incomplete
milestone: 2.1.0 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.