The change_stream_update_lookup_read_concern.js test creates a repl set and assumes that the two secondaries both sync from the primary. In a few cases, the TopologyCoordinator instead syncs one of the secondaries from the other. The test is supposed to temporarily turn off replication on one secondary, but the unfortunate chaining situation means that replication effectively gets disabled on both secondaries, deadlocking the test.

Disabling chaining should prevent this failure from occurring again.