Reproduce --wait-cluster-ready-timeout flag causing linearizability issue

[serathius]

Reproduces https://github.com/etcd-io/etcd/issues/16666 but finds that --wait-cluster-ready-timeout could even cause linearizability issue in single node cluster.

[serathius]

Revision is goes back by 1, for couple of requests and then it is restored. Consistent with predictions in https://github.com/etcd-io/etcd/issues/16666

Think this is combination of 2 issues, https://github.com/etcd-io/etcd/issues/16666 and I expect that in single node clusters, leader trusts it's own db state and doesn't check readIndex, which during bootstrap can be newer then db state.

[ahrtr]

Please integrate https://github.com/etcd-io/raft/pull/105 and try again.

[serathius]

Will do, however I think the https://github.com/etcd-io/raft/pull/105 is not a proper solution. I expect it will fix the issue, but I don't think the approach is correct. Responsed on PR with my thoughts.

[k8s-ci-robot]

@serathius: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-etcd-verify	6edc12a32cc55bd4bfd34948b9c5f2453e2df507	link	true	/test pull-etcd-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.