During the transition to dedicated config we're running removeShard command which drops the sharding metadata. However currently it drops them only on the primary, but not on the secondaries, which needs to be fixed in order to make reads on secondaries not return invalid results for the short period of time before shards realise themselves that the metadata has been dropped.