Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.4] backport ignore old leader leases revoking requests #17465

Conversation

ivanvc
Copy link
Member

@ivanvc ivanvc commented Feb 20, 2024

Backport of PR #16822. Related to #15247.

This PR has three commits:

  1. Fixes the incorrect backport of WaitLeader (PR: [3.4] tests/e2e: backport WaitLeader #17398), as 3.4's spawnJsonCmd receives an expected output string as an argument, which wasn't provided in the first backport implementation.
  2. Completes backporting the remaining e2e cluster setup functions (EndpointsGRPC, EndpointsHTTP) from the original backport from PR: [3.4] Separate grpc server #15620.
  3. Backport of the actual implementation of ignoring old leader leases revoking requests.

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

ivanvc and others added 3 commits February 20, 2024 11:29
Fixes the incorrect backport of WaitLeader, as spawnJsonCmd receives an
expected output string as an argument, which wasn't provided in the
first backport implementation.

Original backport of commit 371179e from
PR etcd-io#17398.

Signed-off-by: Ivan Valdes <ivan@vald.es>
Finish backporting the remaining functions from the original backport
from PR etcd-io#15620.

Backport of commit 65add8c.

Co-authored-by: Marek Siarkowicz <siarkowicz@google.com>
Signed-off-by: Ivan Valdes <ivan@vald.es>
Backport of PR etcd-io#16822, commits f7e488d,
67f1716,
and f7ff898.

Co-authored-by: Benjamin Wang <benjamin.wang@broadcom.com>
Signed-off-by: Ivan Valdes <ivan@vald.es>
@k8s-ci-robot
Copy link

Hi @ivanvc. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@ahrtr
Copy link
Member

ahrtr commented Feb 21, 2024

/ok-to-test

Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Thanks. @ivanvc

cc. @fuweid @jmhbnz @serathius

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants