Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Catalog and Routing
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.