[SERVER-64454] tenant_migration_conflicting_donor_start_migration_cmds.js should not automatically forget migrations Created: 11/Mar/22  Updated: 29/Oct/23  Resolved: 15/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2022-03-21
Participants:
Linked BF Score: 40

 Description   

This first test runs two migrations and expects the second to join the first, but each migration is forgotten as soon as it completes. So, it's possible that the first migration's state doc has already been deleted by the time the second is run. If this happens, we'll fail any assertions that are made around the second migration joining the first. The test should instead wait to forget the migrations until after both have run.



 Comments   
Comment by Githook User [ 14/Mar/22 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-64454 tenant_migration_conflicting_donor_start_migration_cmds.js should not automatically forget migrations
Branch: master
https://github.com/mongodb/mongo/commit/a830b32fb405bf8cf2c5b3c3e92ce5954890daa6

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