-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"tiup mirror clone _ nightly" does not download the actual nightly version of pump/drainer/br/dm/lightning etc. #1108
Comments
I think it's not a good idea to clone nightly because many components don't have And I'm sure you can't run the single command |
The bug here is that components that do have nightly version aren't using nightly due to the whitelist. In particular this breaks pump/drainer cluster when using a mirror of nightly version. |
For each mirror and each component, tiup need at least one stable version for that component (the component could be pre release but not nightly only). So clone nightly (even with The bug exists because we did't consider that someone will try to clone a nightly package, maybe we should forbid cloning nightly rather than support it? BTW, what's your use case to clone a nightly version? Maybe we can find some way else. |
…version (pingcap#1128) * Fix the issue that the default selected version may be a preprelease version Close pingcap#1119 Partly fix pingcap#1082 * Add test * Test * Fix nightly * Fix test * Fix nightly clone Close pingcap#1108 Co-authored-by: Ti Chi Robot <71242396+ti-chi-bot@users.noreply.github.com>
Bug Report
Please answer these questions before submitting your issue. Thanks!
First, clone the tiup mirror following https://docs.pingcap.com/tidb/dev/production-offline-deployment-using-tiup:
Then, get a list of components with nightly version but not properly filled in:
Empty list
tiup --version
)?The reason we get this is because #271 is incomplete.
tiup/pkg/repository/clone_mirror.go
Lines 420 to 421 in 74dfe6f
tiup/pkg/repository/clone_mirror.go
Lines 432 to 435 in 74dfe6f
Pump, Drainer, BR, DM and Lightning are not listed as a
coreSuites
, so when encountering the pseudo-version "nightly", it enters the branch in line 434 and get the latest stable version instead (v5.0.0-rc). This in turn yanks the true nightly version, and set the"nightly"
field in the manifest to empty. So when we deploy a nightly cluster containing binlog using this local mirror, it fails with "component not found" error.This bug can be worked-around by specifying the exact nightly version (e.g. using
v5.0.0-nightly-20210128
instead ofnightly
everywhere).The text was updated successfully, but these errors were encountered: