[SERVER-55811] upgrade_downgrade_sharded_cluster.js does not properly check the upgrade from lastContinuous (4.9) to latest (5.0) Created: 06/Apr/21 Updated: 29/Oct/23 Resolved: 06/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Jordi Serra Torrens |
| 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: | Sharding EMEA 2021-05-03 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
When we test theĀ setFCV from 4.9 and 5.0 we shouldn't check whether the distributionMode and the dropped fields exist since they were unconditionally removed in the 4.9 binary. |
| Comments |
| Comment by Githook User [ 06/Apr/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |