eHoldings app unusable in Honeysuckle official release

@Sobha Duvvuri @Khalilah Gambrell @Oleksii Petrenko, I created a bug related to unexpected work of status endpoint. The remaining work will be done in the https://folio-org.atlassian.net/browse/MODKBEKBJ-550#icft=MODKBEKBJ-550.

@Pavlo Smahin: My observation is that UI always requested the status from backend. In Goldenrod, backend would return a 200 with "isConfiguration" : false where as in Honeysuckle - backend is returning a 500. Please see screenshots below.

Open

Open

@Pavlo Smahin status endpoint shouldn't be used in settings. From the code it looks like we aren't showing any errors if the request fails.. but it seems that we actually are showing it. Need to investigate it a bit more
cc: @Sobha Duvvuri

@Sobha Duvvuri
It is expected behavior for GET /status endpoint when there are no valid credentials.
It should be possible to update the dummy credentials from UI. We should ask FE team why they use status endpoint in settings.
cc: @Denys Bohdan

@Pavlo Smahin: I deployed v3.6.4 to our environment and I am able to confirm that the DB schema error(different schemas for different tenants) got fixed. However, the app is still unusable from the UI because the GET /status endpoint fails with a 500 - Rest of the information in the ticket description is still valid. Attached are the logs.

Open

I am able to workaround the problem by hitting the api directly by making a PUT request to

to replace dummy creds with real ones and then eHoldings app works ok. But, we can't configure it from the UI.