[SERVER-55801] Fix Authorization Contract state tracking during setFCV Created: 05/Apr/21 Updated: 29/Oct/23 Resolved: 07/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0 Required |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Mark Benvenuto |
| 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: | Security 2021-04-19 | ||||
| Participants: | |||||
| Linked BF Score: | 54 | ||||
| Description |
|
The Authorization Contract code is guarded by a feature flag. It makes a check before a command is run and after a command is run. When running setFeatureCompatibilityVersion, the code feature flag may be disabled before the command but enabled after it was run. This disagreement in the state of the feature flag causes causes the code to trigger incorrect assertions since the contract state may not have been cleared when it should have been. |
| Comments |
| Comment by Githook User [ 07/Apr/21 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |