As exposed in our testing infrastructure, it seems like a config stepdown can cause a drop collection to be missed by both shards, leaving the cluster in a state where all shards agree the collection is sharded, but mongos knows it is not sharded.