The test attempts to restart nodes during a resharding operation. This can result in the following situation:

• resharding operation chooses Timestamp T=0
• replica set advances stable timestamp to T=1
• secondary restarts and sets the minimum valid snapshot timestamp to be the stable timestamp
• resharding operation attempts to scan the config.transactions table at T=0 on the secondary
• resharding receives a SnapshotUnavailable error since the collection instances do not match because we created a new PIT collection instance.