--ssh none failed to execute on hosts with dns not ip
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
Please answer these questions before submitting your issue. Thanks!
- What did you do?
tiup cluster deploy c1 v4.0.4 topology.yml --ssh none, topology looks like below:
global:
user: tidb
group: pingcap
# enable_tls: true
tidb_servers:
- host: n4
pd_servers:
- host: n1
- host: n2
- host: n3
- host: n6
- host: n7
- host: n8
- host: n9
- host: n10
- host: n11
- host: n12
- host: n13
- host: n14
- host: n15
- host: n16
- host: n17
- host: n18
- host: n19
- host: n20
tikv_servers:
- host: n1
- host: n2
- host: n3
monitoring_servers:
- host: n3
grafana_servers:
- host: n3
alertmanager_servers:
- host: n3
- What did you expect to see?
Successful deployment
- What did you see instead?
- What version of TiUP are you using (
tiup --version)?
master
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
Start with the tiup cluster deploy command and reproduce the failure using the supplied topology with hostname aliases such as n1 and --ssh none. Inspect the deployment path that handles hostnames when SSH is disabled; done means the topology deploys successfully with DNS names rather than IP addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100