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]

[ti-chi-bot]

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 rolling restart
2. do volumebackup

What did you expect to see?

1. volumebackup success
2. The pause schedule lasts for a short period of time

What did you see instead?

1. volumebackup is stuck, when exceed Volume Backup Init Job Max Active Seconds, volumebackup is set to failed

[ti-chi-bot]

This issue is restored for #5583, it originally created at 2024-03-20 03:28:42.