Refreshing a mirror leads to errors for clients using that mirror
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
The setup here is a single machine that has internet access and will function as a TiUP mirror to other machines.
- What did you do?
On the mirror host do tiup mirror clone... etc to create a clone. Then every so often update the mirror.
Then on another host try to use the updated mirror.
- What did you expect to see?
A functioning mirror allowing all machines in the network to install and update tiup components
- What did you see instead?
Error: read manifest from mirror(http://ti-mirror.sqldb/compound/) failed: invalid signature for file timestamp.json: not enough signatures (0) for threshold 1 in timestamp.json
- What version of TiUP are you using (
tiup --version)?
# tiup --version
1.10.2 tiup
Go Version: go1.18.3
Git Ref: v1.10.2
GitHash: 2de5b500c9fae6d418fa200ca150b8d5264d6b19
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
Reproduce the issue with tiup mirror clone and a subsequent mirror update, then inspect the mirror refresh and timestamp-signature verification paths. Done means clients can use the refreshed mirror to install and update TiUP components without the timestamp.json signature error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100