In an attempt to minimize the duration that there is no writable primary, the resharding test fixture will ask the secondaries nicely to step up. However, if the config server is also a shard, it's likely that the config shard accepts writes often enough that no secondary will ever be able to get voted in due to being too stale (see this comment for an example of this).

Consider introducing a new mode to stepUpNewPrimaryOnShard that is more aggressive (e.g. by using replSetStepDown instead) and modify resharding_coordinator_recovers_abort_decision.js to use it here, since this test requires a failover in order to succeed.