P2-[4.0-bug-hunting]-[TiUP]- edit config (import from ansible) leads to unexpect change
Opened this issue · 2 comments
gekaiwen commented
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. What did you do?
- deploy cluster by TiDB-ansible
- import TiDB cluster with TiUP
- edit config with TiUP, update any other value
tiup cluster edit-config tidb-test -R tidb
2. What did you expect to see?
config which I updated change, others not change.
3. What did you see instead?
monitored:
deploy_dir: deploy/monitor-9100
data_dir: data/monitor-9100
log_dir: deploy/monitor-9100/log
change to
monitored:
deploy_dir: deploy/monitor-9100
data_dir: data/monitor-9100
log_dir: deploy/monitor-9100/deploy/monitor-9100/log
4. What version of TiDB are you using? (tidb-server -V
or run select tidb_version();
on TiDB)
tiup cluster -v
Starting component cluster: /home/tidb/.tiup/components/cluster/v0.6.2/cluster -v
tiup version v0.6.0 (Unknown/Unknown) go1.13
============================
https://github.com/pingcap-incubator/tiup-cluster/blob/master/pkg/meta/topology.go:618 maybe should add some check~
shuke987 commented
/bug P2
lonng commented