Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.7
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:
- sharding-wfbf-day

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-05-17
Linked BF Score:
70
Confidence Status:
None
Work Order:
3

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

The setDefaultRWConcern command run by the run_fuzzer_restore_cluster_settings.js hook is only allowed in FCV 4.4. We should ensure the cluster is in FCV 4.4 before attempting to run the setDefaultRWConcern command.

Note that it isn't sufficient to skip running the setDefaultRWConcern command when the server isn't in FCV 4.4 because it is possible for the FCV 4.2 downgrade to have been interrupted and for the cluster-wide default read and write concerns to still be set to nonsensical values by the fuzzer.

is related to

SERVER-51333 setFeatureCompatibilityVersion should fail when downgrading from FCV 4.4 to FCV 4.2 with long collection names present

Closed

SERVER-53359 jstestfuzz (mutational) fuzzer is forcing last-lts FCV during validate instead of latest

Closed

related to

SERVER-57557 [v4.4] Support running checkFCV() shell helper with mongos connection

Closed

Assignee:: Max Hirschhorn
Reporter:: Max Hirschhorn
Participants:: Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: May 14 2021 05:33:47 PM UTC
Updated:: Oct 29 2023 09:53:32 PM UTC
Resolved:: May 17 2021 03:48:08 PM UTC
Confidence Status Last Update:: 14/May/21 5:58 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates