[SERVER-48199] Prevent ShardingTests from being used without journaling in curop_auth_info.js Created: 13/May/20  Updated: 29/Oct/23  Resolved: 28/May/20

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

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Spencer Jackson
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
Sprint: Security 2020-05-18, Security 2020-06-01
Participants:
Linked BF Score: 34

 Description   

Sharding is working to remove {shardAsReplicaSet: false} from the ShardingTest fixture. We'll want to remove that test option from the auth tests. Unfortunately, this means that ShardingTest will require a journal to correctly instantiate a cluster.

curop_auth_info.js had its shardAsReplicaSet flag removed, but wasn't blacklisted from the noJournal Evergreen variant. We'll probably want to avoid exercising that part of the test on that build variant.



 Comments   
Comment by Githook User [ 27/May/20 ]

Author:

{'name': 'Spencer Jackson', 'email': 'spencer.jackson@mongodb.com', 'username': 'spencerjackson'}

Message: SERVER-48199 Avoid ShardingTests without journaling in curop_auth_info.js
Branch: master
https://github.com/mongodb/mongo/commit/c6ad955d35137efbc1dee40a346b195a54b860cd

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