Closed motjuste closed 5 months ago
I am not sure why some of the Juju 2.9 integration tests fail as I do not believe I have modified any code related to those failures. The integration tests for Juju 3.1.6 pass.
The problem I am trying to debug is the issue #310 on Juju 3.1.6 on top of microk8s 1.24 that I have been banging my head against while trying to deploy the MLFlow bundle. I hope that this change will help me debug that issue better.
@motjuste , latest merge added exception logging - if you believe it's enough I would like to close this PR
@motjuste , latest merge added exception logging - if you believe it's enough I would like to close this PR
Hi ... sorry for late response ... looks good, since logger.exception
will also add the exception info. You are free to close this PR, or let me know if I should.
Issue
When connection to
mysqlsh
is checked, anyMySQLClientError
is swallowed. This does not help with debuggability.Solution
Change the API from returning a
bool
to returning nothing, but promising the faithfully throw an exception while checkingmysqlsh
connection if one occurred, without losing any information that can help with debugging. The call-site can then do the same, better here with a higher-level error, but again, without losing any details of the original error.