SERVER-139166Needs Scheduling
fassert 12436504 "Attempted to reserve optime without a declared write intent" in LocalOplogInfo::getNextOpTimes via TransactionParticipant::performNoopWrite
h3. Summary A {{mongod}} 9.0.5 shard primary aborted with fatal assertion 12436504, {{"Attempted to reserve optime without a declared write intent"}}, raised from {{LocalOplogInfo::getNextOpTimes}}. The node did not recover and stayed down until the test fixture tore the cluster down ~12 minutes later. Found in MongoDB CI for the mongosync (Cluster-to-Cluster Sync) project, in a suite that repeatedly kills and restarts {{mongos}} processes against a 2-shard cluster while a migration is running