prometheus is not started after upgrade from 5.1.4 to 6.15 in arm env
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
-
What did you do?
arm env
install 5.1.4 tidb cluster and then upgrade it to 6.1.5
after upgrade check status of this cluster -
What did you expect to see?
all components are normal
- What did you see instead?
Prometheus is not started when tiup response "upgrade successfully"
this issue only exist in arm env
4. What version of TiUP are you using (tiup --version)?
[root@tiup-0 ~]# tiup --version
1.9.1 tiup
Go Version: go1.17.7
Git Ref: v1.9.1
GitHash: 8c9d75df55c48e3cd645c2eea1fb0c51cfcd92d0
[root@tiup-0 ~]#
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ARM upgrade from TiDB 5.1.4 to 6.1.5 with TiUP 1.9.1, then inspect the upgrade handling for the Prometheus component. Done means the upgrade reports success and the cluster status shows Prometheus started and all components normal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100