If a collection is dropped and re-created (under a different uuid that's compared larger than the old one) on the donor during recipient failovers, when the new recipient primary tries to resume the collection cloning stage, it is possible to hit this uassert with NamespaceExists if the old recipient primary already created the collection of the same namespace under the old uuid.