[SERVER-46749] Pin node binary versions for multiversion tests with unclean shutdowns Created: 10/Mar/20  Updated: 06/Dec/22  Resolved: 05/Nov/21

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

Type: Task Priority: Major - P3
Reporter: Jason Chan Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Duplicate Votes: 0
Labels: multiversion-tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Related
is related to SERVER-58343 Re-enable reshard_collection_failover... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Currently, multiversion tests don't support the scenario where a node with the latest binary version goes through an unclean shutdown and then restarting with a downgraded binary. These tests are currently blacklisted from the multiversion suites.

Instead, we should consider pinning the node binary version for tests with unclean shutdowns so that restarting the nodes will not start with a random binary version. This will allow us to get multiversion coverage for these tests.



 Comments   
Comment by Brooke Miller [ 05/Nov/21 ]

We added dedicated downgrade suites which we believe should provide enough coverage for the downgrade scenario.

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