Giters

pingcap / tiup

A component manager for TiDB

Home Page:https://tiup.io

Repository from Github https://github.compingcap/tiupRepository from Github https://github.compingcap/tiup

Scaled component version doesn't respect `component_versions` in the original spec

djshow832 opened this issue · comments

commented

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
  1. Create a spec with component_versions:
component_versions:
  tiproxy: "v1.0.0"
  tidb: "nightly"
  1. Create a cluster with v8.2.0:
tiup cluster deploy my_cluster v8.2.0 cluster.yaml -y
tiup cluster start my_cluster
  1. Scale out tidb and tiproxy:
tiup cluster scale-out my_cluster scale-out.yaml

Note that the version is not specified in scale-out.yaml.

  1. Check the versions of scaled tiproxy and tidb

  2. What did you expect to see?

The scaled version of tiproxy and tidb should be the same as other instances. That is, TiDB nightly and TiProxy v1.0.0

  1. What did you see instead?

Scaled TiProxy and TiDB are the latest stable versions. TiDB v8.2.0 and TiProxy v1.1.0

  1. What version of TiUP are you using (tiup --version)?
1.16.0 tiup
Go Version: go1.21.11
Git Ref: v1.16.0
GitHash: e543145831d44a863366ff8c379d25980730bbd1
commented

/assign