Invalid elasticsearch host name or port will result in config tool goes to unexpected status

Description of problem:

When input invalid Elasticsearch host name or port in config-tool web console and trigger validation, got a error popup window to show "Could not validate configuration, please report this error".

Version-Release number of selected component (if applicable):

quay 3.8.1
registry.redhat.io/quay/quay-operator-rhel8@sha256:5b549ee6c6bffb3c92390c8959873d7b29cc9d6393a93831f65b8c2236d33690
registry.redhat.io/quay/quay-rhel8@sha256:67132c68b4e5231de5981dc65e1c97cab3b56170534ccc09e2352a4d319f04ee

How reproducible:

always

Steps to Reproduce:
1.  set up a workable Elasticsearch
2.  configure Elasticsearch in config-tool web console
3.  input invalid Elasticsearch host name or port 

4. click "Validate Configurations Changes"

Actual results:

Got a popup window to show "Could not validate configuration, please report this error"

Expected results:

config-tool should report the error by a normal way, such as what the invalid Elasticsearch password got

Additional info:

This problem should exist for long time,  it is very possible for quay 3.7 to have this problem.

Uploaded the logs of quayregistry-quay-config-editor pod in the attachments.