The test performs the following operation

• create an invalid index
• drop the invalid index
• run validateDbMetadata and check no errors are returned

However, due to migrations the following might happen:

• Drop starts
• Migration from shard0 to shard1 starts
• Migration starts creation of index on shard1
• Drop index drops on shard0 but not shard1 (not committed yet)
• Migration now commits the create index on shard1

in this case, we have left an invalid index on shard1, which will make the test failing. The test should stay black-listed until PM-2077 is completed which should solve the known issue.