Testsuite bugs

[DanaSunal]

• ServiceLayer / BasicPart / /v1/list-ltps-and-fcs / Acceptance / vs oam put - 26 Requests in the folder

Iteration: 1 - dummy es-c/index-alias (test passes) fails on 500 Internal Server Error

with request body

{
  "elasticsearch-client-interface-1-0:index-alias": "walckpwhrvem"
}

Elasticsearch throws:

Elasticsearch error occurred: {"error":{"root_cause":[{"type":"invalid_alias_name_exception","reason":"Invalid alias name [walckpwhrvem]: an index or data stream exists with the same name as the alias"}],"type":"invalid_alias_name_exception","reason":"Invalid alias name [walckpwhrvem]: an index or data stream exists with the same name as the alias"},"status":400}

which suggests, that the same index alias was used in some previous test.

• ServiceLayer / BasicPart / /v1/update-operation-client / Continuous Integration / Service Idempotent? - 2 Requests in the folder

Request body is formed with undefined parameters:

{
  "application-name": "ElasticSearch",
  "release-number": "1.0.0",
  "old-operation-name": "undefined",
  "new-operation-name": "undefined"
}

I believe this is because ElasticSearch does not have any operations, which means it should be excluded from the randomized input.

[IswaryaaS]

For point#1, need to include a request that deletes the dummy index in ES through API directly from testcases after testing for index-alias is completed.
Also, in services like /v1/redirect-topology-change-information and core-model-1-4:control-construct (OAM Layer), this step of reverting index-alias shall be included.