Fix Cluster Connection issue on MC - TLS OpenSSL Usage [DEX-357]

[ihsandemir]

There is an issue when adding a cluster connection in MC while both MC and the cluster are running on separate EC2 machines. After uploading the client config in MC (see the attached example, where you can update the address and cluster name), the following error appears:

Request URL:
http://3.210.202.95:8080/api/clusters
Request Method:
POST
Status Code:
500 Server Error
Remote Address:
3.210.202.95:8080

{
    "error": {
        "type": "GENERAL_EXCEPTION",
        "message": "An exception occurred: Handler dispatch failed; nested exception is java.lang.NoClassDefFoundError: io/netty/buffer/ByteBufAllocator"
    }
}

STEPS TO REPRODUCE:

Create a new simulator benchmark using hazelcast5-tls-ec2 template

Update inventory_plan.yml to provision 1 member machine, 1 client machine, 1 MC machine

Setup inventory

Run a test for at least 10 mins to be able to access a running cluster

See https://hazelcast.atlassian.net/browse/DEX-357

Open MC using http://<mc_host_ip>:8080

Add new cluster connection

Select Upload Client Config

Upload client-hazelcast.xml (use example in the attachment)

Observe current behaviour

ACTUAL RESULT: Cluster connection is not added. Error java.lang.NoClassDefFoundError: io/netty/buffer/ByteBufAllocator in MC.

EXPECTED RESULT: Cluster connection is successfully added.

See https://hazelcast.atlassian.net/browse/DEX-357