[CI] DocsClientYamlTestSuiteIT class failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic-platform-support #6969 / ubuntu-2004-aarch64_checkpart1_platform-support-arm
• elasticsearch-periodic-platform-support #6942 / sles-15_platform-support-unix
• elasticsearch-periodic-platform-support #6878 / windows-2019_checkpart1_platform-support-windows
• elasticsearch-periodic-platform-support #6878 / windows-2022_checkpart1_platform-support-windows
• elasticsearch-pull-request #61486 / part-1-windows
• elasticsearch-periodic-platform-support #6871 / windows-2019_checkpart1_platform-support-windows
• elasticsearch-periodic-platform-support #6871 / windows-2022_checkpart1_platform-support-windows
• elasticsearch-pull-request #61413 / part-1-windows
• elasticsearch-pull-request #61413 / part-1-windows
• elasticsearch-periodic-platform-support #6864 / windows-2022_checkpart1_platform-support-windows

Reproduction Line:

undefined

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

• [8.x] 30 failures in class org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT (3.2% fail rate in 933 executions)
• [8.x] 9 failures in step windows-2022_checkpart1_platform-support-windows (42.9% fail rate in 21 executions)
• [8.x] 8 failures in step windows-2019_checkpart1_platform-support-windows (40.0% fail rate in 20 executions)
• [8.x] 9 failures in step part-1-windows (90.0% fail rate in 10 executions)
• [8.x] 11 failures in pipeline elasticsearch-periodic-platform-support (52.4% fail rate in 21 executions)
• [8.x] 5 failures in pipeline elasticsearch-pull-request (4.6% fail rate in 108 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

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

[nielsbauman]

I had a quick look at all the linked build scans and I'm seeing a few different things:

• The most common one is

   java.lang.AssertionError: Failure at [reference/cat/nodes:15]: field [$body] was expected to match the provided regex but didn't	
   Expected: ip        \s+heap.percent \s+ram.percent \s+cpu \s+load_1m \s+load_5m \s+load_15m \s+node.role \s+master \s+name\s* 127.0.0.1           \s+\d+ \s+\d+ \s+\d+    \s+(\d+\.\d+( \s+\d+\.\d+ \s+(\d+\.\d+)?)?)?                  \s+.+       \s+[*]      \s+.+\s*	
        but: was "ip        heap.percent ram.percent cpu load_1m load_5m load_15m node.role   master name\n127.0.0.1           59          39  -1                          cdfhilmrstw *      node-0\n"
  

  See this example build scan. Someone should have a look at this to check what's going on.
• But I'm also seeing

   java.lang.AssertionError: Failure at [reference/troubleshooting/common-issues/disk-usage-exceeded:78]: got unexpected warning header [	
   	299 Elasticsearch-8.19.0-a85f65f951ce7132d699cc42230404060f876dc0 "this request accesses system indices: [.security-7], but in a future major version, direct access to system indices will be prevented by default"	
   ]
  

  and

   java.lang.AssertionError: Failure at [reference/rest-api/common-options:235]: Expected a map containing	
      metadata: a map containing	
         indices: a map containing	
   my-index-000003: a map containing	
               state: "open"	
   my-index-000002: a map containing	
               state: "open"	
   my-index-000001: a map containing	
               state: "open"	
       .security-7: <unexpected> but was <{state=open}>
  

  in this and this build scan respectively. Both of these are caused by the recent changes to the security index. @slobodanadamovic, I fear we're going to keep running into issues (also considering the ones that are still open). Do you happen to have any suggestions on a more systematic approach to tackle/prevent these test failures? They're only test failures (not actual production issues), so the "only" impact they have is on us ES engineers, but I'd like to avoid these from showing up if possible.

[nielsbauman]

I'm not changing the risk yet because I'm not sure what the cause/impact of the first failure type is.

[slobodanadamovic]

Sorry for not handling these earlier. I've been swamped with other tasks.
I've raised #124684, which disables the feature for docs YAML tests.
There is no real need for this feature to be enabled in all YAML tests.