[CI] CcsCommonYamlTestSuiteIT test {p0=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section} failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic #5920 / openjdk17_checkpart1_java-fips-matrix
• elasticsearch-intake #16017 / part1

Reproduction Line:

./gradlew ":qa:ccs-common-rest:yamlRestTest" --tests "org.elasticsearch.test.rest.yaml.CcsCommonYamlTestSuiteIT" -Dtests.method="test {p0=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section}" -Dtests.seed=E06C38975F3A4BFB -Dtests.locale=en -Dtests.timezone=Pacific/Wallis -Druntime.java=17 -Dtests.fips.enabled=true

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [search.vectors/41_knn_search_bbq_hnsw:146]: 
Expected: <3>
     but: was <2>

Issue Reasons:

• [8.x] 2 failures in test test {p0=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section} (1.4% fail rate in 139 executions)

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

[elasticsearchmachine]

This has been muted on branch 8.x

Mute Reasons:

• [8.x] 2 failures in test test {p0=search.vectors/41_knn_search_bbq_hnsw/Vector rescoring has same scoring as exact search for kNN section} (1.4% fail rate in 139 executions)

Build Scans:

• elasticsearch-periodic #5920 / openjdk17_checkpart1_java-fips-matrix
• elasticsearch-intake #16017 / part1

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)

[carlosdelest]

It looks like we're missing a refresh for the indices when adding data, as sometimes we get just 2 results instead of the expected 3. Triaging as low risk, will put up a PR soon to fix this