[SERVER-61634] ShardingTest tries to perform write without proper auth Created: 19/Nov/21 Updated: 29/Oct/23 Resolved: 15/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Sanika Phanse (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam3, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2022-06-27 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Story Points: | 2 | ||||
| Description |
|
here. It should probably be wrapped inside the authutil.asCluster like the few lines below it or maybe just remove it? Not sure if it's needed given that initiating a replica set should generate writes on the primary. Resulting with the logs:
|
| Comments |
| Comment by Githook User [ 14/Jun/22 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |