There seems to be a race condition, when an automatic reconfig is being asynchronously scheduled by a primary(for newlyAdded field removal), and right after that a stepdown is taking place , so that during execution of the reconfig routine the node is primary, but the stepdown has already started and thus terms are not promoted.