[SERVER-75748] Fix checkMetadataConsistency uassert error message Created: 06/Apr/23  Updated: 29/Oct/23  Resolved: 13/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Sharding EMEA 2023-04-17
Participants:

 Description   

In these two uassert (1, 2) we wrongly mention "aggregate" command.

Instead we should say somenthing like:

"checkMetadataConsistency command on admin database can only be run without collection name. Found unexpected collection name: \{collName}"



 Comments   
Comment by Githook User [ 13/Apr/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-75748 Fix checkMetadataConsistency uassert error message

(cherry picked from commit a96b2024a5d8f564cd6f0ca76502266f90681c3e)
Branch: v7.0
https://github.com/mongodb/mongo/commit/7850e039bcd3a7a9ea30d6d05830c689a725503f

Comment by Githook User [ 12/Apr/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-75748 Fix checkMetadataConsistency uassert error message
Branch: master
https://github.com/mongodb/mongo/commit/a96b2024a5d8f564cd6f0ca76502266f90681c3e

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