[SERVER-57255] Don't delete steady state constraint options when backporting to 5.0 Created: 27/May/21  Updated: 29/Oct/23  Resolved: 03/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Siran Wang (Inactive) Assignee: Siran Wang (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-multiversion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to SERVER-57408 Complete TODO listed in SERVER-57255 Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-06-14
Participants:
Linked BF Score: 20
Story Points: 1

 Description   

Currently, we will set the oplogApplicationEnforcesSteadyStateConstraints parameter for nodes in a mixed version cluster. After apply the new multiversion fixture API, this parameter should remain when backport to 5.0.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 03/Jun/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-54622 Retrieve back-branch fixture files to assemble multiversion

SERVER-57255 Don't delete steady state constraint options when backporting to 5.0

(cherry picked from commit 846a99de9a02454c5649cfaa4e69c785ddbfca62)
Branch: v5.0
https://github.com/mongodb/mongo/commit/93f992a39f79880139bac75cc463dced6b6ea7f8

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