Enterprise KMIP tests are not working

[pehala]

Issue description

Configuration file hytrust-kmip-ear.yaml, points to a server that no longer works, so tests SCT_Enterprise_Features/EncryptionAtRest/EaR-longevity-kmip-200gb-6h-test and SCT_Enterprise_Features/EncryptionAtRest/EaR-longevity-kmip-200gb-6h are currently broken. They fail with with [shard 0:main] init - Startup failed: std::system_error (error system:111, Connection refused)

Logs

• test_id: 8c89cbef-bacd-4198-a0e5-d76e6a083345
• argus: https://argus.scylladb.com/test/84260ef4-1a0d-43e8-ba5c-1f9292850c17/runs?additionalRuns[]=8c89cbef-bacd-4198-a0e5-d76e6a083345

[pehala]

This test is broken, i.e. it assume there a KMIP server, that server is down and broken.

someone should do some work:

to spin up a server in a way it can be recreated. or spin up a pykmip server, as done in dtest and core testing

until one of those things happens, kmip can be test in SCT.

From @fruch in the Argus

[mykaul]

@pehala - what's the latest status?

[pehala]

No progress, this basically requires to rethink how we deal with KMIP in SCT in general.