If the IndexBuildsCoordinator fails to acquire the locks for the index build, it may leave the index build, with its corresponding BackgroundOperation, in an unfinished state. This can happen when the createIndexes is invoked with a short maxTimeMS duration.

The resulting inconsistent may affect subsequent metadata operations such as collections drops and renames that check BackgroundOperation::assertNoBgOpInProgForNs().

This is applies only when the IndexBuildsCoordinator is enabled for the createIndexes command.