We never check whether ConfigServer::replicaSetChange was able to successfully update the shard list with the newly updated seed list and this could leave the seed list in config servers to be outdated for a long time since this only gets triggered once ReplicaSetMonitor sees that the local replica set host list it has is different from isMaster.