Closed karolyczovek closed 3 years ago
The current UT already cover the functional test, I assume it was always tested with fully configured tenantdb setup
Is a forced push with squashed commits fine for you, or shall I open a new PR with?
Is a forced push with squashed commits fine for you, or shall I open a new PR with?
Yes, good enough
The current UT already cover the functional test, I assume it was always tested with fully configured tenantdb setup
I mean that we don't test the scenario where the exception is raised, and the tenant with the error is not added to the connectors list. It is pretty basic test, but it is not covered now. We would simply need to add a new test, really similar than: https://github.com/SUSE/hanadb_exporter/blob/master/tests/db_manager_test.py#L59
For example, the mock_conn3
would raise this exception that we now catch, and finally the _db_connectors
list wouldn't have this element.
Could you add this test? Otherwise I can add it to this PR
Could you add this test? Otherwise I can add it to this PR
Please add it, i am buried deeply into beloved Hana
Merged. Thanks @karolyczovek
This patch adds exception handling when not all tenant dbs have the monitoring user enabled.