Juju 3.1.7 not compatible with charm

[MiaAltieri]

Following the tutorial features such as TLS and set password fail

[github-actions]

https://warthogs.atlassian.net/browse/DPE-3241

[petrutlucian94]

I'm also trying out 3.1.7 and noticed that setting the password while having more than one replica fails, so does adding units after the password has been changed: https://paste.openstack.org/raw/buaZAn4gSgXEPBQrvpEg/.

Apart from the TLS issue, another bug that I've encountered is that s3 integration doesn't seem to work. It looks like the PBM mongo URI doesn't get set: https://paste.openstack.org/raw/bkl408Ga27tt673Appxb/

[petrutlucian94]

I can confirm that downgrading the juju agent to 3.1.5 fixes the set-password action and the TLS relation.

About TLS: I saw that recent versions of the tls-certificates-operator no longer accept the generate-self-signed-certificates setting, I think self-signed certificates were moved to a separate charm called self-signed-certificates, however it doesn't seem to work with the MongoDB charm, not even with 3.1.5: https://paste.openstack.org/raw/bAfBg3OblutUUA7A2naP/. The mongodb unit hangs in a blocked state with (not reachable/healthy). We currently have to use the legacy channel of tls-certificates-operator.

[gruyaume]

For self-signed certificates, yes please use the self-signed certificates operator. If the charm has issues that prevent it from being used with MongoDB, please describe what those issues are and open an issue in its Github project. We'll adapt the charm as necessary. Please don't use the legacy tls-certificates-operarator, it is unmaintained and won't receive any fix.

On this note, I observed that MongoDB is using a quite old version of the tls-certificates library. It's using 1.12 and the latest available is 2.21. I'm not sure if that's the issue but that for sure won't help.

[MiaAltieri]

@petrutlucian94

Thank you for all your helpful comments here as of eariler this week #331 merged and now 6/edge should be functional on 3.1.7 i.e. password, TLS should work.

I will update 5/edge now.

As for TLS without self-signed certificates there is active work being done to look into this.

[petrutlucian94]

That's great, thanks for letting me know about the fix. I've tried the edge version of the mongodb charm with the latest stable juju version (3.3.0) and everything worked fine: https://paste.opendev.org/raw/byZi6G3HB7ZWbsvB51bY/. TLS configuration was applied correctly using the self-signed-certificates charm and backups completed successfully.

There's just one small nit, not sure if it's expected or not: there are a few Unknown operation result messages in the charm log: https://paste.opendev.org/raw/b3kFxID7BTvecAzUceBl/