The onStepUpComplete function of ReplicaSetAwareService is called before we update _canAcceptNonLocalWrites, so when the services are performing their step up we are not actually primary yet. Most services spawn an async function to perform complex stepup work and that means with the removal of the RSTL in SPM-4164 we needed to treat these cases carefully since they can execute code before we are a write accepting primary.

Going forward we should find a way to reduce confusion around this interface, since when onStepUpComplete is called step up isn't actually complete yet