[SERVER-82205] Make shell dbHash comparison to exclude encryption options Created: 16/Oct/23  Updated: 29/Oct/23  Resolved: 19/Oct/23

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

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

Issue Links:
Depends
Related
related to SERVER-68122 Investigate replicating the collectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution EMEA Team 2023-10-30
Participants:
Linked BF Score: 40

 Description   

SERVER-68122 introduced a change that makes secondaries not replicate into the durable catalog any encryption option passed to the primary. This was intended, as it served as a way to avoid crashes due to non-existent encryption keys.

However, SERVER-79496 banned the option altogether and introduced a new test to this effect. This test is now being used in the fuzzer and causes dbHash mismatches in the shell since nodes do not have the same collection config metadata across nodes.

We are already doing some collection info manipulation today to avoid getting false-positives during testing here. We should consider scrubbing the encryption options from testing as well since we are deliberately allowing them to differ across nodes now.



 Comments   
Comment by Githook User [ 18/Oct/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-82205 Sanitize config string options in dbHash shell method
Branch: master
https://github.com/mongodb/mongo/commit/9f49101645a5d21784a89df563f81ae83e9017ed

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