Fix flaky FLS challenge test geo field fallback #162729

Merged
seanzatzdev opened 3:35pm on October 20, 2026 wanted to merge 21 Ξ” into elastic/elasticsearch main from
fix-fls-challenge-geo-fallback

Pull Request Overview

  • Opened on October 20, 2026
  • Status Merged
  • Commit count 1 with first commit October 20, 2026

Total Delta

21 Total Diff Delta

Open Days

Open 10 weekdays

Test Delta

0 Diff Delta in Test Files
Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Fraction of total time Business days Phase
 
0.1 days Authoring 1 commit before pull request opened for review
 
0.3 days Awaiting first review
 
10.0 days Merge to deploy (still awaiting deployment)

Total time for pull request 0.4 business days from first commit authored to merge
Still awaiting deployment

Author avatar

Fix flaky FLS challenge test geo field fallback

randomDeniedField() in StandardVersusLogsdbFieldLevelSecurityChallengeRestIT excludes geo_point, geo_shape and shape (DENY_INCOMPATIBLE_FIELD_TYPES) only when picking a field from the mapping template. If the template has no compatible field, it falls back to a top-level field from the indexed documents, and that path did not check the type. It could therefore deny a geo_point, which hits the known standard vs logsdb FLS difference the exclusion exists to avoid.

This applies the same type exclusion in the fallback.

Verification:
- Without the fix, seed F7C3E98DC8B5F055 (-Dtests.locale=en-AG -Dtests.timezone=US/Eastern) at commit 2e7beaba873d (the Sep 28 failing build) fails with Values of type [geo_point] don't match after normalization.
- With the fix, the same seed at the same commit passes.
- With the fix on current main, 100 iterations pass. The seed no longer reproduces on main without the fix, because data generation changed after Sep 28.

The test is not muted in this repo. The mute for the issue is in elasticsearch-serverless and needs removing once this reaches serverless.

related: elastic/elasticsearch-serverless#7542

Comments Threads Pending Resolution

Resolved Comment Threads

No resolved comments have been left on this PR.