It looks like a time-series insert can return a plain 'Interrupted' error code after a stepdown (at least in certain circumstances) rather than the expected 'InterruptedDueToReplStateChange', resulting in the operation not being retried.

This resulted in BF-25238. We have a band-aid fix (SERVER-67533) to exclude the test from the relevant concurrency passthroughs for the time being, but we would like to get to the root cause. It only seems to affect time-series inserts, not regular collections, and it only seems to happen in the sharded concurrency passthroughs with stepdowns involved.

In the continuous stepdown suites, you get the 'Interrupted' error code with a default error message. In the kill_primary suites, you get the 'Interrupted' error code with a more descriptive error message about read preference, like "Write results unavailable from failing to target a host in the shard shard-rs0 :: caused by :: Could not find host matching read preference { mode: \"primary\" } for set shard-rs0".