At present if a collection has a default collation configured, sharding such a namespace via Ops Manager results in a failure with the following symptom: ``` [13:21:17.050] Plan execution failed on step ShardCollections as part of move ShardCollections : [13:21:17.050] Failed to apply action. Result = : [13:21:17.050] Error calling shardCollection on sh.myColl with key = [[a 1]] : [13:21:14.994] Error executing WithClientFor() for cp=mubuntu:27017 (local=false) connectMode=AutoConnect : [13:21:14.993] Error running command for runCommandWithTimeout(dbName=admin, cmd=[{shardCollection sh.myColl} {key [{a 1}]} {unique false}]) : result={} identityUsed=mms-automation@admin[[MONGODB-CR/SCRAM-SHA-1]][24] : (BadValue) Collection has default collation: collation: { locale: "fr", caseLevel: false, caseFirst: "off", strength: 3, numericOrdering: false, alternate: "non-ignorable", maxVariable: "punct", normalization: false, backwards: false, version: "57.1" }. Must specify collation {locale: 'simple'} ``` In addition there is no way to specify a default collation if a collection is created via Ops Manager UI. Please add support of default collation.