this assertion in wildcard_index_feature_compatability_version.js expects a 4.0 binary to reject a wildcard index that it finds in its catalog on startup. In most cases this is correct, but we have seen at least one scenario where the 4.0 binary mongod will start up without having fully built and persisted the wildcard index before being shut down last time. In such a scenario the mongod will attempt to rebuild the index before figuring out that it doesn't recognize the index specification, resulting in a different error code: 40590.

Even though the test waits for replication before shutting down the secondaries, it's still possible that the index build hasn't finished at that point. We should update the test to account for this possibility.