[SERVER-58696] Re-enable implicit_default_write_concern_add_shard.js in all sharding suites Created: 20/Jul/21 Updated: 29/Oct/23 Resolved: 05/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Moustafa Maher |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Repl 2021-08-09 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
After the test is fixed, it will have to be re-enabled in the sharding_auth, sharding_auth_audit, sharding_update_v1_oplog, etc. suites from which it has been disabled as a part of So we should have to make changes only to the yml file for the above suites, along with the actual bug fix itself. This test has currently been added to the "exclude_files" section of all the suites. Also, please see |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 05/Aug/21 ] |
|
Author: {'name': 'Moustafa Maher', 'email': 'm.maher@10gen.com', 'username': 'moustafamaher'}Message: |
| Comment by Tommaso Tocci [ 27/Jul/21 ] |
|
m.maher it seems jstests/sharding/cwwc_conflict_add_shard.js has been also disabled for the same issue, do you think we can also re-enabled it as part of this ticket? |