pingcap / pingcap/tiup

tiup v1.11.0 Error: failed to fetch cpu-arch or kernel-name

Open
#2,050 1 comment 0 reactions 0 assignees View on GitHub

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!

  1. What did you do?
tiup cluster check ./topology.yaml -i /home/pengdaqian.0/.ssh/id_rsa --ssh system
  1. What did you expect to see?

deploy succeed

  1. What did you see instead?
tiup is checking updates for component cluster ...
Starting component `cluster`: /home/xxxx/.tiup/components/cluster/v1.11.0/tiup-cluster check ./topology.yaml -i /home/xxxx/.ssh/id_rsa --ssh system

+ Detect CPU Arch Name
  - Detecting node 0.0.0.0 Arch info ... Error

Error: failed to fetch cpu-arch or kernel-name: executor.ssh.execute_failed: Failed to execute command over SSH for 'xxxx@0.0.0.0:22' {ssh_stderr: , ssh_stdout: , ssh_command: export LANG=C; PATH=$PATH:/bin:/sbin:/usr/bin:/usr/sbin /usr/bin/sudo -H bash -c "uname -m"}, cause: signal: killed
  1. What version of TiUP are you using (tiup --version)?
tiup -v                                                                          
1.11.0 tiup
Go Version: go1.19.1
Git Ref: v1.11.0
GitHash: 1a4714d7146fa85240a1ff4ef7451df719e0b4f0
(base)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the tiup cluster check path and the SSH executor named in the error, then reproduce the command against the reported topology. Trace the remote uname -m execution and verify the check can fetch CPU architecture and kernel information over SSH without the reported failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.