Skip to content

Issues: pingcap/tidb-operator

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.

Sign up for GitHub

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

285 Open 1,676 Closed
285 Open 1,676 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Backup cleanup taks fail when using azure storage account and Kubernetes
#5975 opened Dec 13, 2024 by viniciusvarzea
expose tikv metrics port in tikv peer service
#5970 opened Dec 10, 2024 by plevart
I would like to add allowPrivilegeEscalation
#5961 opened Dec 2, 2024 by JacksonChen63
4
Release 1.6.1
#5957 opened Nov 25, 2024 by csuzhangxc
2 of 8 tasks
Does tidb-operator have no requirements for the k8s version? Are any version of k8s and any version of tidb-operator compatible?
#5953 opened Nov 18, 2024 by xiaoxiongxyy
1
Dependency Dashboard
#5839 opened Nov 5, 2024 by renovate bot
88 tasks
TiDB-operator is unable to delete TiProxy servers
#5835 opened Nov 4, 2024 by kos-team
2
TiDB operator cannot scale up the tiflash after scaling down to 0
#5834 opened Nov 4, 2024 by kos-team
3
TiDB-operator fails to start the tiproxy servers if spec.tiproxy.version not provided
#5833 opened Nov 4, 2024 by kos-team
5
If store number is 0, it is expected to set the volume backup to failed which will not blocked the whole clean schedule [restore for 5658] area/ebs-br type/bug Something isn't working
#5821 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
A TiKV was restarted before it was stopped for scheduling, and BR did not exit in a timely manner and set the status to failed, resulting in the cluster remaining in the pause schedule state [restore for 5583] area/ebs-br type/bug Something isn't working
#5820 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
tikv crash during volumerestore [restore for 5577] area/ebs-br type/bug Something isn't working
#5819 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
volumebackup will failed when there is more than 50 tags specified in snapshot [restore for 5540] area/ebs-br type/bug Something isn't working
#5818 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
volumebackup failed when backup restored cluster [restore for 5537] area/ebs-br type/bug Something isn't working
#5817 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
Stuck restore during data restore caused by stale peer [restore for 5531] area/ebs-br type/bug Something isn't working
#5816 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
If there is a PV with the same name (released status) in the namespace, it will cause the restore to fail [restore for 5505] area/ebs-br type/bug Something isn't working
#5815 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
volumebackup failed, error message is "init job deleted before all the volume snapshots are created" [restore for 5478] area/ebs-br type/bug Something isn't working
#5814 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
Pausing lighting will cause a loss of status when encountering a TikV restart, and backup needs to be set to fail [restore for 5442]
#5813 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
TiKV failed for more than 5 minutes, and the system did not set the backup task as failed [restore for 5439] area/ebs-br type/bug Something isn't working
#5812 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
backup should be set to failed when error "failed to keep importing to store 17 being denied, the state might be inconsistency" occured [restore for 5437] area/ebs-br type/bug Something isn't working
#5811 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
When checking whether warmup has ended, if there are warmup jobs in other namespaces, it will interfere with the current results. [restore for 5405] area/ebs-br type/bug Something isn't working
#5810 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
volumeback failed. reason is "Pod backup-fed-ebs-tidb-operator-ebs-1-init-w5glk has failed, original reason " [restore for 5330] area/ebs-br type/bug Something isn't working
#5809 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
do volumebackup after scaling out cluster, backup failed [restore for 5306] area/ebs-br type/bug Something isn't working
#5808 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
delete restore data pod when restoring will cause restore progress stuck [restore for 5297] area/ebs-br type/bug Something isn't working
#5807 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
kill restore-data pod will cause restore failed [restore for 5295] area/ebs-br type/bug Something isn't working
#5806 opened Oct 25, 2024 by ti-chi-bot
@BornChanger
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.