[SERVER-49436] Change migrations_with_mixed_fcv.js test to reflect current FCV/migration interactions Created: 10/Jul/20  Updated: 29/Oct/23  Resolved: 12/Aug/20

Status: Closed
Project: Core Server
Component/s: Sharding, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-48192 investigate the failures in the targe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-08-10, Sharding 2020-08-24
Participants:

 Description   

The following changes need to be made:

  • Migrations should succeed on both source and destination up/downgrade.
  • Since there is no longer a writeConcern parameter mismatch on latest and last-stable, we should remove the test case testMigrateFromLastStableToLatest or just assert it succeeds
  • FCV no longer blocks on a migration, so we should test the inverse.

Once this is complete, remove the migrations_with_mixed_fcv.js test blacklists.



 Comments   
Comment by Githook User [ 12/Aug/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-49436 Change migrations_with_mixed_fcv.js test to reflect current FCV/migration interactions
Branch: master
https://github.com/mongodb/mongo/commit/3813db066fdfc4a7ace1047aee8bc286caf0b443

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