MongoDB Charm Breaks Cluster Creation When Auth=True

[Joel Johnston]

Trying my best to actually secure MongoDB when I deploy it via Juju. So far no luck.

I'm able deploy a 2 node cluster successfully via juju if auth default = False. I've tried following modern instructions for securing mongo post-installation by adding --auth to the systemctl unit. This causes juju to fail to be able to run commands on any of the nodes.

I'm able to deploy a 1 node cluster via juju if auth default = True. However, I have no way to authenticate against the database and can't find a username/password anywhere online. So that's useless.

If I pull down the charm and change auth default = True and deploy a 2 node cluster, the post installation steps for creating the replica set fails with:

mongodb/0* error idle 0 <my-ip-range>.96 27017/tcp,27019/tcp,27021/tcp hook failed: "replica-set-relation-changed"
mongodb/1 maintenance executing 1 <my-ip-range>.97 27017/tcp,27019/tcp,27021/tcp no replset config has been received

So far as I can see (and have read) the MongoDB charm is unusable in its current state. Please advise.

Thank You,

Joel

[Charles Clark (charlesweb)]

Joel, how did you end up getting around this show-stopper? Are you deploying your cluster manually now or using a different software suite?

[Joel Johnston (joeldjohnston)]

I have not gotten around it, just using this in a sandbox environment to test against Mongo. I'll have to use terraform or something else to deploy s production worthy cluster.

[Charles Clark (charlesweb)]

Thanks for the info, Joel. I haven't setup authentication yet on my sandbox either but when I try I'll see if I can see what could be done to the charm to enable it.