Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 安装部署集群报Error: Operation aborted by user (with answer ‘’) (tui.operation_aborted)
|
username: TiDBer_xgwIsUrp
[TiDB Usage Environment] Production Environment
[TiDB Version] V7.60
[Reproduction Path] Deployment
[Encountered Problem: Phenomenon and Impact] The error is as follows: There are two options written below, but when executing the deployment command (tiup cluster deploy tidb-yfhis v7.6.0 ./topology.yaml --user root -p), it exits directly. The last segment is a red error. Can anyone tell me what is going on? Is it a configuration file issue? How to handle it?
Attention:
1. If the topology is not what you expected, check your yaml file.
2. Please confirm there is no port/directory conflicts in the same host.
Do you want to continue? [y/N]: (default=N)
Error: Operation aborted by user (with answer ‘’) (tui.operation_aborted)
Configuration file is as follows:
16:30 Tried switching tools, same error and termination; also tried manually generating the configuration file, still the same error. It shouldn’t be related to the version, right? I downloaded TiDB 7.6.0-DMR
----- Downloaded a lower version, still the same error
19:46 Latest update: Found that the configured SSH trust is unstable, it actually failed, is it because the trust was not configured properly?
Supplementary mutual trust configuration process:
Run the command on Host A
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub Host B
ssh-copy-id -i ~/.ssh/id_rsa.pub Host C
ssh-copy-id -i ~/.ssh/id_rsa.pub Host D
ssh-copy-id -i ~/.ssh/id_rsa.pub Host E
The problem was resolved in the morning, thanks everyone. Due to recent project matters, I haven’t had time to reproduce the issue. The resolution process was as follows:
- Re-established the trust relationship of the hosts, and re-ran the trust-related steps script for tiup
- Regenerated the yaml file with the script, edited and saved it using the VI tool
- Repaired it again using the tiup tool script
Then, running the command worked.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: