[CI] CoreWithSecurityClientYamlTestSuiteIT test {yaml=health/10_basic/cluster health basic test} failing about elasticsearch HOT 5 OPEN

Pinging @elastic/es-security (Team:Security)

from elasticsearch.

Assigning to security team due to the test name, but it may be health node related?

The CoreWithSecurityClientYamlTestSuiteIT runs all YAML tests against the cluster which has security enabled. This means that this test is not security related per se, it depends which underlying YAML test was executed.

The health check is being returned as "unknown" likely because the health service has not yet broadcasted the health information from each node needed.

The failure reproduces locally for me, and I think your assumption is correct here. I don't see anything pointing to the security issue. I will transfer it to @elastic/es-data-management team for further triage.

Edit: Also this test has been skipped for a while. It looks like it was unmuted recently. Which explains why we are seeing it fail now.

from elasticsearch.

Pinging @elastic/es-data-management (Team:Data Management)

from elasticsearch.

Yeah looking at the response, we see that most things are green, but:

        "disk" : {	
          "status" : "unknown",	
          "symptom" : "No disk usage data."	
        },	
        "shards_capacity" : {	
          "status" : "unknown",	
          "symptom" : "Unable to determine shard capacity status."	
        },

And then immediately after the response is written, we get this logged out:

[2024-04-23T17:38:46,977][INFO ][o.e.h.n.s.HealthNodeTaskExecutor] [test-cluster-0] Node [{test-cluster-0}{dpTxDhG1R12ljlIh_gXjmw}] is selected as the current health node.	

I think that this is yet another test where we really need a ?wait_for_status=green param on the health report api.

from elasticsearch.

Another failure on 8.13: https://gradle-enterprise.elastic.co/s/oo7y7w2ue2imw

from elasticsearch.