Upgrade may skip bootstrap ver221 from specified branch
Open
severity/major
sig/sql-infra
type/bug
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Bug Report
Please answer these questions before submitting your issue. Thanks!
### 1. Minimal reproduce step (Required)
Upgrade TiDB from customer branch `release-8.5-20250606-v8.5.2` to `release-8.5` (v8.5.6+).
### 2.Reason
The customer branch already used bootstrap version `221` for different changes. During upgrade, TiDB only executes bootstrap steps with a greater bootstrap version, so the upstream `upgradeToVer221` step is skipped, leaving `mysql.tidb_pitr_id_map` schema not updated (e.g. missing `restore_id` and/or incorrect PRIMARY KEY).
### 4. What is your TiDB version? (Required)
`release-8.5-20250606-v8.5.2`
Contributor guide
Assessment
This issue has not been assessed yet.