© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f399f05
demo site
(Get the code!)
I don't believe we've ever released a Juju 2.1.4, so I'm a little curious what binary you are running. It sounds like maybe you are running from source in the 2.1 branch?
Can you also describe what OS you are running on? LXD picking 192.168.0.3 address seems a bit surprising. I'm thinking possibly trusty?
This doesn't really seem to have much to do with HA or not HA, as much as there seems to be an issue around 'juju restore' trying to create a user that already exists. oploger@admin certainly feels like a Mongo internal account (it sounds like the account in charge of tracking the local oplog and sharing it to replicas).
Now, we always launch Mongo with --replSet and --oplog because if you ever want to migrate from a single Mongo instance to multiple, you have to start the first one in a compatible mode.
I'm also curious if there is something like you're taking a backup on Trusty but restoring to Xenial (or vice versa). Some of those can have an effect because Trusty only has Mongo 2.4, while we use Mongo 3.2 on Xenial. I would guess that mongo doesn't support downgrading (so taking a backup of a 3.2 couldn't be restored to a 2.4), but that doesn't seem to be what you're encountering.
Have you tried doing backup and restore without HA in the middle to narrow down if it is just 'juju restore' that isn't working for you, vs restore after-HA?