Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.6
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:
- tig-dataconsistency

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
STM 2018-12-17
Linked BF Score:
14
Story Points:
2
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

~~SERVER-36718~~ made the changes so that we can use forceValidationWithFeatureCompatibilityVersion to upgrade the servers before validating the collections. But BF-10462 is a case when a downgrade in the test was interrupted and there is no way for the validation hook to start the upgrade in the middle of a downgrade. Therefore, the validation hook should first downgrade and then upgrade in this case.

causes

SERVER-44613 ValidateCollections hook does not call setFCV(4.2) if a test leaves the FCV at "upgrading to 4.4"

Closed

is related to

SERVER-36718 Validation hook should upgrade before validating index consistency

Closed

SERVER-43627 Remove v4.2 FCV handling from ValidationCollections JS test hook

Closed

Assignee:: Max Hirschhorn
Reporter:: Xiangyu Yao (Inactive)
Participants:: Githook User, Max Hirschhorn, Xiangyu Yao
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Sep 11 2018 03:49:33 PM UTC
Updated:: Oct 29 2023 10:28:18 PM UTC
Resolved:: Nov 30 2018 10:41:51 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates