When sharding a collection on the legacy path we check if the shard is the database's primary shard however, this check should be done after checking the database version is up to date, like on the DDL coordinator. There is a complication though, on the multiversion suites, we might have a router on last stable that will send the command through the config server, and this will send the command to the shard without attaching the db version, so, doing this check this way, would cause a compatibility issue with older versions. We should check for the db version only if the request came from a router with the latest version.