encryption: add test for temporary KMS service unavailable#17445
encryption: add test for temporary KMS service unavailable#17445ti-chi-bot[bot] merged 2 commits intotikv:masterfrom
Conversation
|
Hi @hhwyt. Thanks for your PR. I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/pull-unit-test |
There was a problem hiding this comment.
| let fail = (|| { | |
| fail_point!("kms_api_timeout_decrypt", |val| val | |
| .and_then(|x| x.parse::<bool>().ok()) | |
| .unwrap_or(false)); | |
| false | |
| })(); | |
| if fail { | |
| return Err(CloudError::ApiTimeout(box_err!("api timeout"))); | |
| } | |
| (|| { | |
| let fail = fail_point!("kms_api_timeout_decrypt", |val| val | |
| .and_then(|x| x.parse::<bool>().ok()) | |
| .unwrap_or(false)); | |
| if fail { | |
| Err(CloudError::ApiTimeout(box_err!("api timeout"))) | |
| } else { | |
| Ok(()) | |
| } | |
| })()?; |
There was a problem hiding this comment.
I refactored the fail_point part to the following simplified version. Let me know if you have any thoughts or suggestions!
fail_point!(fail_point_name, |val| {
val.and_then(|x| x.parse::<bool>().ok())
.filter(|&fail| fail)
.map(|_| Err(CloudError::ApiTimeout(box_err!("api timeout"))))
.unwrap_or(Ok(()))
});|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LykxSassinator, overvenus The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
ref tikv#17410 This commit adds a new test to verify TiKV's recovery after temporary unavailability of the KMS service. Signed-off-by: hhwyt <[email protected]>
|
@hhwyt: Your PR was out of date, I have automatically updated it for you. If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions 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 ti-community-infra/tichi repository. |
|
/pull-unit-test |
|
/retest |
|
@hhwyt: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
/retest |
|
In response to a cherrypick label: new pull request created to branch |
ref tikv#17410 Signed-off-by: ti-chi-bot <[email protected]>
ref tikv#17410 Signed-off-by: ti-chi-bot <[email protected]>
|
In response to a cherrypick label: new pull request created to branch |
ref tikv#17410 Signed-off-by: ti-chi-bot <[email protected]>
|
In response to a cherrypick label: new pull request created to branch |
ref #17410
This commit adds a new test to verify TiKV's recovery after temporary unavailability of the KMS service.
What is changed and how it works?
Issue Number: Ref #17410
What's Changed:
Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note