Indices.Exists returns false even if the index exists for ES 7.2.0

NEST/Elasticsearch.Net version: 7.0.1 Elasticsearch version: 7.2.0 Description of the problem including expected versus actual behavior: Regardless of whether the index exists or not the function

Indices.Exists("IndexName").Exists

always returns false.

This can be observed for Indices.ExistsAsync too.

Calling HEAD accesslogs in the dev console will return “200 - OK”

Steps to reproduce:

1. Create an index in dev console
2. Write a console app that calls “Indices.Exists().Exists” function for index created in step 1
3. Observe that the return is false instead of expected true

[ffMathy]

Same problem here. It has re-emerged. Also .NET Core and latest NEST.

[jwagon]

I am reproducing this consistently with Elasticsearch 7.3.0 and NEST 7.1.0

With code like:

var result = _client.Indices.Exists("ms-core-integration-test");

result.IsValid comes back false, as does result.Exists. result.ServerError is null.

The index definitely exists, I can see (returns 200) it when calling

HEAD /ms-core-integration-test

I am getting this response:

FailureReason: BadResponse while attempting HEAD on https://XXXXXXXX.us-east-1.aws.found.io:9243/ms-core-integration-test

Audit trail of this API call:
- [1] BadResponse: Node: https://XXXXXXXX.us-east-1.aws.found.io:9243/ Took: 00:00:00.0230221
OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 200 from: HEAD /ms-core-integration-test
Request:
<Request stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>
Response:
> > 
Exception:
Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 200 from: HEAD /ms-core-integration-test

That makes no sense, how can the response be invalid but also return 200?

BTW, other operations (search, actually creating the index, etc.) work fine, so it’s not as if I’m not connecting properly.

This is definitely a bug and the client is not behaving as expected. Please re-open.