As part of the drop collection coordinator, dropCollectionLocally is called on each shard. This command calls the catalog dropCollection command which translates all bucket namespaces to their view namespaces. This is done regardless of whether there are actually any timeseries options present for the collection. This means that if I create a bucket namespace (without timeseries options) and then call drop for the view namespace, it will drop my bucket namespace.

This is additionally a problem when we start tracking unsharded collections. In the linked BF, we can see how the translation being done at this level but not at the coordinator level can cause catalog inconsistencies.