Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-77266

createCollection command in rename_capped_collection_droptarget.js should ignore "cannot find ns" errors

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.19, 6.0.8
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Sharding EMEA
    • Fully Compatible
    • v6.0, v5.0
    • Sharding EMEA 2023-06-26
    • 11
    • 1

      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).

            antonio.fuschetto@mongodb.com Antonio Fuschetto
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            0 Vote for this issue
            4 Start watching this issue