[SERVER-46149] The parts of test_stacked_migration_cleanup.js that check persisted range deletion state should not execute if the FCV is last stable Created: 14/Feb/20  Updated: 29/Oct/23  Resolved: 18/Mar/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: sharding-4.4-stabilization, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-03-23
Participants:
Linked BF Score: 49

 Description   

For example, this check should not be done if the FCV is last stable, that is, the test is running in a multiversion suite.



 Comments   
Comment by Githook User [ 18/Mar/20 ]

Author:

{'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-46149 Don't verify persisted range deletion state if FCV is last-stable in test_stacked_migration_cleanup.js
Branch: master
https://github.com/mongodb/mongo/commit/5c3d1e11eef52c1cdc76a5bf66d136af632f07a1

Comment by Githook User [ 12/Mar/20 ]

Author:

{'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-46149 Don't verify persisted range deletion state if FCV is last-stable in test_stacked_migration_cleanup.js
Branch: v4.4
https://github.com/mongodb/mongo/commit/d3b0ed87666bd8845f1ccd2ca7e659db2889d5e3

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