Original Summary

Backport SERVER-32672 fix to 3.6

Original Description

A bug related to LogicalTimeValidator fails converting a 3.6 replica set to sharded cluster. It was fixed in 4.0. We need a backport of this fix to 3.6.

Details:

I was following steps in https://docs.mongodb.com/manual/tutorial/convert-replica-set-to-replicated-shard-cluster/

to convert a replica set to a sharded cluster.

I failed on the step to restart a 3.6 replica set to shard. Once I restart it, I can no longer connect to the replica set/shard. I keep getting errors like

Command failed with error 210 (CannotVerifyAndSignLogicalTime): 'Cannot accept logicalTime: { ts: Timestamp(1560272596, 1) }. May not be a part of a sharded cluster' on server qm3:27101. The full response is {"ok": 0.0, "errmsg": "Cannot accept logicalTime: { ts: Timestamp(1560272596, 1) }. May not be a part of a sharded cluster", "code": 210, "codeName": "CannotVerifyAndSignLogicalTime"}

The same procedure has no problem with 3.4 or 4.0.

I believe the bug is related to https://jira.mongodb.org/browse/SERVER-32672

We are using mongo 3.6 currently and we need to convert our replica sets to sharded clusters. It is not feasible for us to upgrade to 4.0 very soon. Could you backport this fix to 3.6, so that we'll be able to continue using our database?