SERVER-132822ClosedFixed
createIndexes reports success without creating the index when a concurrent moveCollection replaces the collection
{{createIndexes}} can reply {{ok: 1}} without having created the requested index. The client is told the index exists, and any later operation on it fails with {{IndexNotFound}} for example. h2. How it happens # {{createIndexes}} resolves the target collection UUID and releases all locks, then blocks in the {{maxNumActiveUserIndexBuilds}} queue in {{IndexBuildsCoordinatorMongod::_startIndexBuild()}}. The config fuzzer had set the knob to 1, so the wait lasted ~15 seconds. # A concurrent