Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-103707

[test-only issue] Don't run _shardsvrCommitDropDatabaseMetadata and _shardsvrCommitCreateDatabaseMetadata in auth tests when there is a standalone node or replica set

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-04-14, CAR Team 2025-04-28
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      commands_builtin_roles_replset.js and commands_builtin_roles_standalone.js run all tests defined at jstests/auth/lib/commands_lib.js.

      If _shardsvrCommitDropDatabaseMetadata or _shardsvrCommitCreateDatabaseMetadata is run in one of those configurations (replica set or standalone node), the test will fail with a:

      [js_test:commands_builtin_roles_replset] [jsTest] 	"errmsg" : "Cannot accept sharding commands if sharding state has not been initialized with a shardIdentity document",
      [js_test:commands_builtin_roles_replset] [jsTest] 	"code" : 203,
      [js_test:commands_builtin_roles_replset] [jsTest] 	"codeName" : "ShardingStateNotInitialized",
      

      This ticket aims to ban those test cases to be run in standalone or replica set configurations.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: