[SERVER-59792] Ensure FCV cannot change during Merge Created: 03/Sep/21  Updated: 27/Oct/23  Resolved: 15/Oct/21

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

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backport Requested:
v5.1
Sprint: Server Serverless 2021-09-27, Server Serverless 2021-10-04, Server Serverless 2021-10-11, Server Serverless 2021-10-18
Participants:

 Description   

An FCV change on the donor or recipient must be prohibited, or must cause Merge to abort. Audit the existing Multitenant Migrations protocol and make sure it will enforce these rules during Merge.



 Comments   
Comment by A. Jesse Jiryu Davis [ 15/Oct/21 ]

tenant_migration_save_fcv.js tests that we note down the recipient FCV at the beginning of a migration and that a change in that FCV will abort the migration.

tenant_migration_donor_abort_on_fcv_change.jstenant_migration_donor_abort_on_fcv_change.js, tenant_migration_donor_recipient_fcv_mismatch.js, and tenant_migration_donor_recipient_fcv_mismatch_after_failover.js test variations on this.

tenant_migration_donor_recipient_fcv_mismatch.js tests that starting a migration fails if the donor and recipient do not share the same FCV.

 

Generated at Thu Feb 08 05:48:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.