[SERVER-77776] Execution control should not be FCV-gated Created: 03/Jun/23 Updated: 27/Oct/23 Resolved: 06/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||
| Sprint: | Execution Team 2023-06-12 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Execution control should be enabled on any v7.0 binary if the feature flag is enabled; it should not depend on FCV. The current behavior means that when FCV is upgraded to 7.0 on a v7.0 binary, execution control will not start until the server is restarted. |
| Comments |
| Comment by Gregory Noma [ 06/Jun/23 ] |
|
This actually already works as intended because the feature flag check is using `FeatureFlag::isEnabledAndIgnoreFCVUnsafe`. |