Creating connections failed after TiDB enables auto-tls and runs for 30 days
Open
affects-8.1
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
severity/moderate
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)
1. Enable TiDB auto-tls
2. Run for 30 days
3. Connect to TiDB with TLS enabled
### 2. What did you expect to see? (Required)
Creating connection succeeds
### 3. What did you see instead (Required)
Creating connection fails.
Client reports `failed to complete tls handshake: tls: first record does not look like a TLS handshake`.
TiDB logs `TLS Certificate rotation failed` and `malform packet error`.
### 4. What is your TiDB version? (Required)
master
Contributor guide
Assessment
This issue has not been assessed yet.