test: functional test for putBucketIndexes error handling + bump test mongo to 8.0.23

[delthas]

Summary

Adds a functional test for MongoClientInterface.putBucketIndexes error handling — including the case where MongoDB 7.1+ refuses an index build because available disk falls below indexBuildMinAvailableDiskSpaceMB.

Companion to ZENKO-5286 (Backbeat metric for index-creation failures, PR #2750) and ZENKO-5285 (alert for sustained failures).

Commits

1. test: pin mongodb-memory-server to MongoDB 8.0.23 — version bump in package.json. The library default (7.0.14) doesn't enforce indexBuildMinAvailableDiskSpaceMB; the test needs 7.1+ behavior. 8.0.23 also aligns with what Artesca 4.1+ will run in production.

2. test: add functional test for putBucketIndexes error handling — new spec covering three cases:

   • Happy path: valid spec → success
   • indexBuildMinAvailableDiskSpaceMB refusal: MongoDB returns OutOfDiskSpace (code 14031) → Arsenal maps to errors.InternalError. The Backbeat putBucketIndexesFailed metric on ZENKO-5286 fires on this.
   • Spec conflict: existing index name + different keys → IndexKeySpecsConflict → errors.InternalError.

Empirical observation

The disk-kill test confirms MongoDB returns:

{"errmsg":"available disk space of N bytes is less than required minimum of M","code":14031,"codeName":"OutOfDiskSpace"}

Arsenal's existing catch handler at MongoClientInterface.putBucketIndexes correctly maps this to errors.InternalError — same path used by all non-NamespaceNotFound MongoDB errors. The Backbeat conductor's metric is cause-agnostic (fires on any putBucketIndexes error), so this gives us the signal regardless of the specific code.

Notes

• The disk-kill test reads the current indexBuildMinAvailableDiskSpaceMB value via getParameter, sets it to 100 TiB during the test, and restores the original in finally — does not leak state to other tests.
• Smoke-tested diskUsage.spec.js on 8.0.23 — passes (no regressions on the version bump).
• The full mongodb functional suite hasn't been run end-to-end on 8.0.23 yet — CI will validate.

Issue: ARSN-588

[bert-e]

Hello delthas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.92%. Comparing base (5944736) to head (c807144).

Additional details and impacted files

@@               Coverage Diff                @@
##           development/8.4    #2634   +/-   ##
================================================
  Coverage            73.92%   73.92%           
================================================
  Files                  229      229           
  Lines                18480    18480           
  Branches              3847     3822   -25     
================================================
  Hits                 13661    13661           
  Misses                4814     4814           
  Partials                 5        5           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[claude]

LGTM

Review by Claude Code