[SERVER-71486] Fix config settings schema modification during fcv upgrade and downgrade Created: 18/Nov/22 Updated: 29/Oct/23 Resolved: 22/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.2.0-rc1, 6.3.0-rc0 |
| Fix Version/s: | 6.2.0-rc2, 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| 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 | ||||||||
| Backport Requested: |
v6.2
|
||||||||
| Sprint: | Sharding EMEA 2022-11-28 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
There are 2 problems with fcv change and the config settings schema. The first is that during fcv downgrade, we are checking the wrong feature flag to guard the config settings schema code. We need to use gConfigSettingsSchema rather than gGlobalIndexesShardingCatalog. The second is that during fcv downgrade, we are setting the schema to an empty schema and turning the validation level to off. When we upgrade, we add the correct schema, but this doesn't reset the validation level to the default, it stays as off. This means that downgrading and then re-upgrading will leave the validation level as off. |
| Comments |
| Comment by Githook User [ 24/Nov/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit e8d15ab156ca830a970c4bc54e5861fa26173e97) |
| Comment by Githook User [ 22/Nov/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |