If a shard node using a CSRS config server has ever been a chunk donor in a migration, that node will have a minOpTime document stored with the config server's optime from the last migration.

Upon startup or becoming primary, if there is a minOpTime document, the shard starts initializing the ShardingState machinery in order to prime it with the minimal config server optime.

This initialization will never complete if none of the CSRS hosts are available and we will keep retrying infinitely. The reason the initialization gets stuck is because we try to reload the list of shards.

We should change the code so that we can initialize and set the min optime and not reload the list of shards until it becomes necessary.