[SERVER-81205] Add v6.0 test case in skip_level_upgrade.js Created: 19/Sep/23  Updated: 29/Oct/23  Resolved: 26/Sep/23

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

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

Issue Links:
Related
is related to SERVER-76166 Update old LTS version in skip_level_... Open
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-10-02
Participants:

 Description   

skip_level_upgrade.js tests that attempting to startup a latest binary node with old LTS data files will fail and will not corrupt the old datafiles. We currently only run this test against v5.0 — we should add v6.0 here.

We should also consider the following investigation in this ticket: is there a way to automate this list so that we don't have to modify it every LTS release? It's easy to forget to append new versions to the test list, and I wasn't sure if there was a programmatic way to get the old LTS versions. see comment



 Comments   
Comment by Githook User [ 26/Sep/23 ]

Author:

{'name': 'Ali Mir', 'email': 'ali.mir@mongodb.com', 'username': 'ali-mir'}

Message: SERVER-81205 Add v6.0 test case to skip_level_upgrade.js and add TODOs to programmatically generate list of LTS versions in multiversion tests
Branch: master
https://github.com/mongodb/mongo/commit/5e8ceab2454991f5c3600175078d9a6502886a18

Comment by Ali Mir [ 25/Sep/23 ]

I added a section to investigate if we can automate this list, but turns out this was filed in SERVER-76166 already. We should do the investigation in that ticket and just add the v6.0 test case in this one.

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