[SERVER-43037] Update hooks/validate_collections.js to recognize NamespaceNotFound errors in the new error msg form Created: 26/Aug/19  Updated: 29/Oct/23  Resolved: 26/Aug/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
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: Execution Team 2019-08-26
Participants:
Linked BF Score: 0

 Description   

SERVER-42978 changed the validate cmd's error message for NamespaceNotFound from 'ns not found' to "Collection 'test1_fsmdb0.tmpLhDxo.convertToCapped.convert_to_capped_collection_6' does not exist to validate." (for example).

The testing hook running validate cmds, however, filters out by error msg, however, here. which is broken because the error msg changed in SERVER-42978.



 Comments   
Comment by Githook User [ 26/Aug/19 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-43037 Update hooks/validate_collections.js to recognize NamespaceNotFound codeName as opposed to errmsg contents
Branch: master
https://github.com/mongodb/mongo/commit/9d3a90a7f75f453f3a3c6bc6baba26910b89d975

Generated at Thu Feb 08 05:02:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.