© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
Field is seeing exactly this issue on pre-cloud-handover testing on customer site.
$ juju --version
2.6.3-disco-amd64
Steps:
1) juju bootstrap
2) juju enable-ha
After it settles all 3 ha-enabled
3) juju create-backup -m controller
4) juju remove-machine --force 0 1
After they are gone (~2 min)
5) juju restore-backup -m controller --file juju-backup.tar.gz
ERROR could not clean up after failed restore attempt: cannot complete restore: <nil>: Restore did not finish successfully
ERROR cannot perform restore: <nil>: restore failed: error restoring state from backup: setting special user permission in db: server returned error on SASL authentication step: Authentication failed.
Issue also 100% reproduced on AWS provider.
Juju backup-restore documentation says:
"We begin by removing machines ‘1’ and ‘2’ but you can remove any two:
juju remove-machine -m aws:controller 1 2"
https:/
However restore after removing 0 and 1 does not work, after removing 1 and 2 - works fine.
After trying multiple times it falls into this status
$ juju show-controller
juju restore is in progress - API is disabled to prevent data loss
juju restore is in progress - API is disabled to prevent data loss
{}
restore with --debug:
https:/