[SERVER-37647] Validation hook sets FCV to 3.4 no matter what version it currently is Created: 15/Oct/18 Updated: 29/Oct/23 Resolved: 23/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.19 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Xiangyu Yao (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 | ||||
| Operating System: | ALL | ||||
| Sprint: | Storage NYC 2018-10-22, Storage NYC 2018-11-05 | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
In 3.4, the sharded cluster could be in a state where the config servers are in FCV 3.4 but the shard servers are in FCV 3.2. The current validation hook would not upgrade the cluster to 3.4 in this case. However, it is in an intermediate upgrade/downgrade path. |
| Comments |
| Comment by Githook User [ 23/Oct/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: |