[SERVER-84352] Create multiversion upgrade suite Created: 20/Dec/23  Updated: 21/Dec/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:

 Description   

There are currently several suites taking advantage of the should_downgrade parameter to test stepdown + binary replacement scenarios (part of the downgrading process):

$ git grep should_downgrade buildscripts/resmokeconfig/
buildscripts/resmokeconfig/matrix_suites/generated_suites/change_streams_downgrade_last_continuous_new_old_old_new.yml:    should_downgrade: true
buildscripts/resmokeconfig/matrix_suites/generated_suites/change_streams_downgrade_last_lts_new_old_old_new.yml:    should_downgrade: true
buildscripts/resmokeconfig/matrix_suites/generated_suites/retryable_writes_downgrade_last_continuous.yml:    should_downgrade: true
buildscripts/resmokeconfig/matrix_suites/generated_suites/retryable_writes_downgrade_last_lts.yml:    should_downgrade: true
buildscripts/resmokeconfig/matrix_suites/generated_suites/sharded_retryable_writes_downgrade_last_continuous_new_old_old_new.yml:    should_downgrade: true
buildscripts/resmokeconfig/matrix_suites/generated_suites/sharded_retryable_writes_downgrade_last_lts_new_old_old_new.yml:    should_downgrade: true
buildscripts/resmokeconfig/suites/change_streams_downgrade.yml:    should_downgrade: true
buildscripts/resmokeconfig/suites/retryable_writes_downgrade.yml:    should_downgrade: true
buildscripts/resmokeconfig/suites/sharded_retryable_writes_downgrade.yml:    should_downgrade: true
 

Purpose of this ticket is to implement similar capabilities/suites for testing stepdown + binary swap for upgrade since upgrading is a more common use case.


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