pingcap / pingcap/tiup

Validation failed when upgrading to nightly

Open
#2,118 0 comments 0 reactions 0 assignees View on GitHub

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

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

tiup cluster upgrade t6 nightly --offline -y

  1. What did you expect to see?

Success.

  1. What did you see instead?
Error: validation failed for /data3/tidb5/.tiup/storage/cluster/packages/prometheus-nightly-linux-arm64.tar.gz: sha256 checksum mismatch, expect: 6a07e6148cae14113019741495faa57c859662ab060f678ae9b73befa7e41341, got: 7ee8c84e22f7ca4d6f592a7a7b98e113c9d974873ef62962ff13a5db641b6ab1
  1. What version of TiUP are you using (tiup --version)?
1.11.2 tiup
Go Version: go1.19.5
Git Ref: v1.11.2
GitHash: 4c2debca67421ec7b87f91c02032b8fbffa5c9e5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing tiup cluster upgrade t6 nightly --offline -y with TiUP 1.11.2 and inspect the package validation path for prometheus-nightly-linux-arm64.tar.gz. Compare the expected and reported SHA-256 values and determine why the nightly package metadata differs; done means the upgrade validates successfully or reports a corrected, actionable result.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.