Due to SERVER-60933, this fsm workload may encounter "cannot find ns" errors. This behavior was fixed in 7.0 as a part of SERVER-60064, but we cannot backport a fundamental behavioral change to stable release versions.

In order to fix the test on 6.0 and 5.0, we should ignore these errors since it's possible for the collection to have been dropped before the call to listCollections (issued during the createCollection command).