-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Implement terminate failpoint #16788
base: main
Are you sure you want to change the base?
Conversation
f2c5690
to
b97380f
Compare
b97380f
to
5201d18
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Though curious about handling of lazyfs for restarting member, question below.
74da5f4
to
29fd037
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
29fd037
to
3881e06
Compare
/retest |
Oops, looks like test don't pass after rebase. |
3881e06
to
5e4662d
Compare
8c747b5
to
3c3266d
Compare
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
3c3266d
to
aedb627
Compare
Very weird. I have re-implement graceful termination to do the exactly what forceful termination does, but use SIGTERM instead of SIGKILL, still the results are different. In 3 node cluster terminated cluster is unable to bootstrap raft, it hangs somewhere between connecting to other members and publishing member to cluster. Issue doesn't happen in single node cluster. Is there something wrong with e2e testing framework or etcd? cc @ahrtr Added a draft commit to on top for easier reproduction of the issue. |
I think it might be some issue with peer proxy in e2e framework. https://github.com/etcd-io/etcd/actions/runs/8425584127/job/23072006524?pr=16788 |
PR needs rebase. 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-sigs/prow repository. |
@serathius: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
No description provided.