The two initial-sync cases in app_deprioritization_exemption.js share one replica set. The first case adds a node and calls reInitiate(), then only waits until that node is SECONDARY. It does not wait for the automatic reconfig that removes the newlyAdded field and increments the config version.

The second case then adds another node and calls reInitiate() again. That helper reads the current config, increments the version, and submits it. If the newlyAdded removal has already committed the same version, the reconfig fails with NewReplicaSetConfigurationIncompatible.

The new process was started but never received a replica set config. Teardown then tries to freeze that node, gets NotYetInitialized, and assert.soon retries until timeout.

We need to call waitForAllNewlyAddedRemovals() after adding the node to patch this behavior.