In some test executions, we see initiate failing due to initial sync failing to find a sync source. This is because chaining is disabled, which means the node must sync from the primary. However, while the node is going through reconfig, it cannot update its understanding of the primary, and by the time it completes reconfig, it has used up most of its initial sync attempts, leading to an fassert.