During FCV upgrade from 8.0 to 8.1, we moved the sessions collection coordinator from the shards to the config server. This also means that the config server becomes more of a dbPrimary for this collection - it runs the coordinators for it and therefore we expect it to have a copy of the collection locally. We added logic to create the collection locally on the config server since the expectation was that the collection would not exist on the config server. However, if there is a garbage version of the collection locally, this will cause the coordinator to fail. We should clean up the problematic instances of the sessions collection either during FCV upgrade or in the create collection coordiantor before trying to create the collection locally.