[SERVER-73740] Update min_fcv IDL field to handle intermediate FCVs Created: 07/Feb/23 Updated: 29/Oct/23 Resolved: 20/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gabriel Marks | Assignee: | Varun Ravichandran |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Security
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2023-03-06, Security 2023-03-20 | ||||
| Participants: | |||||
| Linked BF Score: | 125 | ||||
| Description |
|
If the min_fcv field of a server parameter is set to an FCV which is not one of the latest, lastContinuous, or lastLTS FCVs, we get a failure at compilation time due to the way we parse the FCV. For example, upon version upgrade to 7.0, we had a min_fcv set to 6.2, which caused a compilation failure as it was not one of latest (=7.0), lastContinuous (=6.3), or lastLTS (=6.0). This is an issue as when a new version releases, we have to fix all min_fcvs to be one of these three versions, which is not ideal. As the FeatureFlag FCV field allow FCVs which are not one of these three, we can probably use what that system does as a baseline for how to proceed. |
| Comments |
| Comment by Githook User [ 20/Mar/23 ] |
|
Author: {'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}Message: |