While investigating BF-26956 we noticed that pre-images replication is tested in initial sync fuzzer tests. This is not desirable as according to the design of the pre-images, they are not replicated during the initial sync process, causing fuzzer test failure.

Pre-images are not added to the fuzzer grammar, however, fuzzer may still generate tests that involve creation of the collections with pre-images being enabled.

We would want to avoid generating and investigating similar BFs in the future. In order to do so we could do:

• set expiration duration to minimum amount (1 second) and ensure that pre-images are deleted after running the test, prior the initial sync process
• adjust the fuzzer code to not generate code related to changeStream pit pre-images (e.g. no create/collMod support for changeStreamPreAndPostImages: enabled)
• add pre-images collection UUID into the ignoreUUIDs of db-hash in run_initial_sync_node_validation.js
• other options (or do nothing as this issue is pretty rare)