A primary runs an automatic reconfig to bump the config term on stepup. If it learned a newer config via heartbeats during catchup mode and drain mode, the auto reconfig may fail, leaving an inconsistent config term with the primary's term.

The primary should not fetch the higher safe config in primary state. It also should not install the new config in _scheduleHeartbeatReconfig_inlock. Force config should always be accepted via heartbeats on primary though.

Consider making the error check on stepup stricter too.