tiup not support package from release bot
Open
Nobody has claimed this yet.
type/duplicate
type/question
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
I used /release in a PR and then got the released package. Then I used tiup patch to upgrade the cluster, but it failed:
[tidb@localhost ~]$ tiup cluster patch example tikv-server.tar.gz -R tikv
Starting component `cluster`: /home/tidb/.tiup/components/cluster/v0.4.9/cluster patch example tikv-server.tar.gz -R tikv
Error: entry tikv-server not found in package tikv-server.tar.gz
Verbose debug logs has been written to /home/tidb/logs/tiup-cluster-debug-2020-04-26-20-01-06.log.
Error: run `/home/tidb/.tiup/components/cluster/v0.4.9/cluster` (wd:/home/tidb/.tiup/data/RxGWtiv) failed: exit status 1
[tidb@localhost ~]$ tar tf tikv-server.tar.gz
bin/tikv-ctl
bin/tikv-server
I tried to patch with binary, it still failed:
[tidb@localhost ~]$ tiup cluster patch example bin/tikv-server -R tikv
Starting component `cluster`: /home/tidb/.tiup/components/cluster/v0.4.9/cluster patch example bin/tikv-server -R tikv
Error: exit status 2
Verbose debug logs has been written to /home/tidb/logs/tiup-cluster-debug-2020-04-26-20-04-04.log.
Error: run `/home/tidb/.tiup/components/cluster/v0.4.9/cluster` (wd:/home/tidb/.tiup/data/RxGXfU7) failed: exit status 1
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 tiup cluster patch commands with the release-bot archive and the bin/tikv-server path shown in the report. Trace how the cluster patch command locates package entries and handles these two inputs; done means both forms can patch the selected tikv role without the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100