[SERVER-44613] ValidateCollections hook does not call setFCV(4.2) if a test leaves the FCV at "upgrading to 4.4" Created: 13/Nov/19  Updated: 29/Oct/23  Resolved: 26/Nov/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-37074 Validation hook should continue downg... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-12-02
Participants:
Linked BF Score: 5

 Description   

Change this code to downgrade FCV to 4.2 when the test left FCV at "upgrading to 4.4".

SERVER-37074 recently made changes to the validate hook to handle the case where FCV is in the middle of being downgraded: "downgrading to 4.2", {version: 4.4, targetVersion:4.2}. However, it also added code such that the hook won't set FCV to 4.2 if FCV is in the middle of being upgraded: "upgrading to 4.4", {version: 4.2, targetVersion:4.4}. It now only sets FCV 4.2 if the test left the FCV at "fully upgraded to 4.4", {version: 4.4}.

Should probably change the if-statement to "if (originalFCV.targerVersion != requiredFCV) setFCV(requiredFCV)"



 Comments   
Comment by Githook User [ 26/Nov/19 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-44613 ValidateCollections hook must always set the expected FCV prior to starting
Branch: master
https://github.com/mongodb/mongo/commit/03f3b000c26146a8194bebb6124623ac0ebf20ec

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