Comment 2 for bug 1671329

Would be interested to compare the shared secrets. Anyways, the test is running the following commands. Probably need to dig in with a manual test to see what's happening:

juju --debug bootstrap --constraints mem=2G google/us-central1 ha-backup-restore-xenial-gce --config /tmp/tmpuu2iwz.yaml --default-model ha-backup-restore-xenial-gce --agent-version 2.2.3 --bootstrap-series xenial
juju --debug list-controllers
juju --debug list-models -c ha-backup-restore-xenial-gce
juju --debug show-status -m ha-backup-restore-xenial-gce:controller --format yaml
juju --debug show-status -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce --format yaml
juju --debug deploy -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce /var/lib/jenkins/repository/charms/dummy-source --series xenial
juju --debug deploy -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce /var/lib/jenkins/repository/charms/dummy-sink --series xenial
juju --debug add-relation -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce dummy-source dummy-sink
juju --debug expose -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce dummy-sink
juju --debug config -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce dummy-source token=One
juju --debug config -m ha-backup-restore-xenial-gce:ha-backup-restore-xenial-gce dummy-source token=
juju --debug enable-ha -n 3 -c ha-backup-restore-xenial-gce
juju --debug restore-backup -m ha-backup-restore-xenial-gce:controller -b --constraints mem=2G --file /mnt/jenkins/workspace/ha-backup-restore-xenial-gce/juju-backup-20170906-231039.tar.gz
juju-restore correctly refused to restore because the state-server was still up.
juju --debug restore-backup -m ha-backup-restore-xenial-gce:controller -b --constraints mem=2G --file /mnt/jenkins/workspace/ha-backup-restore-xenial-gce/juju-backup-20170906-231039.tar.gz