Internal command auth jstest should only run _shardsvrCloneAuthoritativeMetadata with Authoritative Shards

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • ALL
    • Hide

      buildscripts/resmoke.py run --suite=auth jstests/auth/internal_command_auth_validation.js

      On a commit immediately after SERVER-128064 was committed.

      Show
      buildscripts/resmoke.py run --suite=auth jstests/auth/internal_command_auth_validation.js On a commit immediately after SERVER-128064 was committed.
    • CAR Team 2026-06-22
    • 200
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      The internal_command_auth_validation.js jstest validates most internal commands, including _shardsvrCloneAuthoritativeMetadata, require internal authorization (i.e. __system user).

       

      In SERVER-128064 we added a tassert if the command is called with Authoritative Shards disabled. We are hitting this guardrail when the internal_command_auth_validation.js runs this command with Authoritative Shards disabled as part of the non-"all feature flags" EVG variant. This is harmless, but the test fail due to tassert, so we should find a solution.

            Assignee:
            Joan Bruguera Micó
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: