The authoritative metadata cloning DDL coordinator from SERVER-127532 is per-shard, so we may start cloning the authoritative metadata for a DB, only to discover that we are no longer the DB primary due to a movePrimary.

For DB authoritative metadata, we handled this by making movePrimary also make the DB metadata authoritative (SERVER-101625).

However this is not currently the case for collection authoritative metadata. Fix it by cloning the collection authoritative metadata on movePrimary or adding a fallback to the authoritative cloning DDL coordinator.