Open phvalguima opened 4 months ago
This error appears unrelated to setting up TLS on router—I think only the TLS setup on server is relevant here
I think there might be an issue on the server end
On router end, not sure how to handle this better given that we're getting a shell error, not a DBError
We could catch & re-raise this specific exception, but we would miss other shell errors
Trying to add
self-signed-certificates
and relating to mysql-k8s and mysql-router-k8s after they were deployed failed with a transient issue (check below). I call it "transient", as eventually after a quick interval, the issue passes and the charm is able to progress.It seems we had a disconnection from mysql-k8s as it is also setting up its own certificates. I think we should catch this exception in two places:
"/var/lib/juju/agents/unit-mysql-router-k8s-0/charm/src/workload.py", line 297, in status
: catch the subprocess exception and re-raise it in a more meaningful exception within the framework, depending on what is the error"/var/lib/juju/agents/unit-mysql-router-k8s-0/charm/src/relations/tls.py", line 136, in save_certificate
: and deferring the call, or running atenacity.retry
to try reconnect with Mysql.