[SERVER-64636] Ensure that unsupportedOldFCV is still too old in the future git tag variant Created: 18/Mar/22  Updated: 29/Oct/23  Resolved: 23/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Xuerui Fa Assignee: Xuerui Fa
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Repl 2022-04-04
Participants:
Linked BF Score: 48

 Description   

Since the future git tag variant uses a future FCV as latest, the last-continuous FCV in that variant is the current latest FCV on master. For instance, latest is currently 6.0, which means in the future git tag variant, last-continuous is 6.0, which means last-lts is 5.0. As a result, unsupportedOldFCV in set_feature_compatibility_version.js is actually calculated as 5.0, which means the setFCV command will succeed when we expect it to fail. We can resolve this by decrementing unsupportedOldFCV by 2 instead of 1. Alternatively, we can disable the test in the future git tag variant, but I don't feel that that is necessary if this will allow us to keep testing setFCV.



 Comments   
Comment by Githook User [ 22/Mar/22 ]

Author:

{'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}

Message: SERVER-64636: Ensure that unsupportedOldFCV is still too old in the future git tag variant
Branch: master
https://github.com/mongodb/mongo/commit/9b6d19aa8cf204a67307611a6333905359b7aa3f

Generated at Thu Feb 08 06:00:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.