-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
3
-
Execution Team 2020-03-09, Storage Engines 2020-03-23, Storage Engines 2020-04-06
The multiversion evergreen suite appears to expect in various tests that you can run 4.4 on a previous (before 4.2) version. However currently this can result in 4.4 altering the metadata file and making it unreadable for previous version. Is it reasonable to update the multiversion test suite to change this expectation?
One test in particular is the mulitversion/skip_level_upgrade.js test, which intentionally skips levels when running mongod.
- depends on
-
SERVER-46785 Forbid 4.4 mongod binaries from starting up on 4.0 data files
- Closed
- duplicates
-
SERVER-47068 Remove repair lock file when WT salvage refused to work on incompatible data files
- Closed
- is duplicated by
-
WT-5933 Fix failure of skip_level_upgrade test of multiversion suite on Enterprise RHEL 6.2
- Closed