Canonical Juju

  1. Bug #1771657
  2. Comment #10

Comment 10 for bug 1771657

Revision history for this message
John A Meinel (jameinel) wrote :

And interesting part from the pastebin:
20:19:20 DEBUG juju.rpc server.go:329 error closing codec: write tcp 192.168.1.157:46182->3.80.228.179:17070: i/o timeout
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.
20:19:20 DEBUG cmd supercommand.go:496 error stack:
restore failed: error restoring state from backup: setting special user permission in db: server returned error on SASL authentication step: Authentication failed.

That makes me think 'restore' is trying to login to Mongo as the "admin" user, rather than as a machine-agent. (eg, login as machine-2 when restoring on machine 2.)

I believe "juju bootstrap" sets up "admin" credentials on the initial database, but "enable-ha" only sets up machine agent credentials on the other machines. (I could be wrong, as it seems like users should be replicated in HA anyway, but maybe there is a local-admin.)