During SERVER-110665 we had to exclude jstests/concurrency/fsm_workloads/random_moveChunk/random_moveChunk_timeseries_meta_updates.js and jstests/concurrency/fsm_workloads/random_moveChunk/random_moveChunk_timeseries_arbitrary_updates.js as the call for shardedColl.update fails with

Error: write failed with error: {
         	"nMatched" : 0,
         	"nUpserted" : 0,
         	"nModified" : 0,
         	"writeError" : {
         		"code" : 175,
         		"errmsg" : "Update plan failed after having partially executed :: caused by :: placement version mismatch detected for test9_fsmdb0.system.buckets.fsmcoll0"
         	}
}

(See them here)

The failure happens as fuzztest runs the SetClusterParameter DDL, which leads to a conflicting operation in progress, however a trivial assert.soon didn't fix the issue.

The investigation ticket is about to find out if we can fix it and if so, how.