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

When the restore data pod fails, the volumerestore task status is not set to failed [restore for 5293] #5804

Open
ti-chi-bot opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels
area/ebs-br type/bug Something isn't working

Comments

@ti-chi-bot
Copy link
Member

Bug Report

What version of Kubernetes are you using?

What version of TiDB Operator are you using?

What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?

What's the status of the TiDB cluster pods?

What did you do?

  1. do volumerestore
  2. do chaos, Kill restore data container process

What did you expect to see?

  1. volumerestore status is failed

What did you see instead?

  1. volumerestore is running
    d963e3f5-0616-4104-8573-ece477b5d3b1
    f1401891-c047-48c2-8e11-ce29658939bf
@ti-chi-bot ti-chi-bot added area/ebs-br type/bug Something isn't working labels Oct 25, 2024
@ti-chi-bot
Copy link
Member Author

This issue is restored for #5293, it originally created at 2023-09-21 07:55:03.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ebs-br type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants