[SERVER-31910] blacklist mongos_validates_writes.js from the config stepdown suite Created: 10/Nov/17 Updated: 30/Oct/23 Resolved: 16/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.0-rc3 |
| Fix Version/s: | 3.6.0-rc5, 3.7.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||
| Sprint: | Sharding 2017-11-13, Sharding 2017-12-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
This test should be blacklisted because it creates a collection, calls movePrimary, then calls shardCollection and moves a chunk to the old primary (see the linked Any other tests that do this should also be blacklisted from the config stepdown suite. Note: Many of our other tests do call enableSharding, ensurePrimaryShard, then shardCollection and moveChunk. But they don't |
| Comments |
| Comment by Githook User [ 16/Nov/17 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |
| Comment by Githook User [ 16/Nov/17 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |