The test `change_stream_pre_image_startup_recovery.js` has been flaky inside the `no_passthrough_disagg_override` test suite on disaggregated storage.
The test spuriously timed out while trying to step up one of the replica set members. The step-up failed because the replica set member has a priority 0 attached to it. This priority is auto-assigned to the second replica set member node by the injected test fixture for disaggregated storage.
When stepping up the secondary, the test spuriously failed with `NodeNotElectable` errors ("Node was unable to step up because it has priority 0 and is unelectable").
A potential fix is to assign a hard-coded non-0 priority to both replica set members for this test, so that the step-up does not fail because of a wrong priority.
This fixes the `NodeNotElectable` errors on step-up, but the test still fails non-deterministically, as it spuriously runs into the problem described in WT-16663 / SLS-7198.
The fix intermittent failures of this test on disaggregated storage, this change will exclude the test from running in the `no_passthrough_disagg_override` until the issue is fixed in WT.
This PR leaves TODO markers for the two tickets at the exclusion site, so that the test can later be re-enabled.