[SERVER-70595] The enableSharding command should correctly handle requests where the primary Shard ID is encoded as a connection string Created: 14/Oct/22  Updated: 29/Oct/23  Resolved: 17/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
Participants:
Linked BF Score: 35

 Description   

The enableSharding command accept an optional primaryShard parameter, which may represent either a Shard ID or a connection string.  While the the logic to add the entry to the catalog is able to support both encodings, some of the checks behave incorrectly when a connection string gets received



 Comments   
Comment by Githook User [ 17/Oct/22 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-70595 Fix error checks in enableSharding
Branch: master
https://github.com/mongodb/mongo/commit/7dd71ded76ed22c254b297edfb0485a28cd9aec8

Generated at Thu Feb 08 06:16:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.