[SERVER-65803] Exclude shard_encrypted_collection.js from CSRS stepdown suite Created: 19/Apr/22 Updated: 29/Oct/23 Resolved: 20/Apr/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: | Erwin Pe | Assignee: | Erwin Pe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2022-05-02 | ||||
| Participants: | |||||
| Linked BF Score: | 47 | ||||
| Description |
|
The tests in shard_encrypted_collection.js expect the sharded cluster to return InvalidOptions error code when trying to shard/reshard/refine using an encrypted field as the shard key. In the CSRS stepdown suite, this error response is not always guaranteed to be InvalidOptions, as the config server can fail and cause the overall reshard operation to return ReshardCollectionAborted. |
| Comments |
| Comment by Githook User [ 20/Apr/22 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |