pingcap / pingcap/tiup

scale out tikv failed( fedora OS )

Open
#1,499 2 comments 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?

SSH type: builtin
tiup cluster scale-out clustername scale.tikv.yaml -u root -p

Target host system version Fedora release 33 (Thirty Three)

ssh -V
OpenSSH_8.4p1, OpenSSL 1.1.1i FIPS  8 Dec 2020
  1. What did you expect to see?

  2. What did you see instead?

2021-07-26T14:10:38.862+0800    INFO    Execute command finished        {"code": 1, "error": "executor.ssh.execute_failed: Failed to execute command over SSH for 'two@10.10.5.87:22' {ssh_stderr: , ssh_stdout: , ssh_command: export LANG=C; PATH=$PATH:/usr/bin:/usr/sbin sudo -H bash -c \"test -d /home || (mkdir -p /home && chown two:$(id -g -n two) /home)\"}, cause: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain", "errorVerbose": "executor.ssh.execute_failed: Failed to execute command over SSH for 'two@10.10.5.87:22' {ssh_stderr: , ssh_stdout: , ssh_command: export LANG=C; PATH=$PATH:/usr/bin:/usr/sbin sudo -H bash -c \"test -d /home || (mkdir -p /home && chown two:$(id -g -n two) /home)\"}, 

cause: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain\n at github.com/pingcap/tiup/pkg/cluster/executor.(*EasySSHExecutor).Execute()\n\tgithub.com/pingcap/tiup/pkg/cluster/executor/ssh.go:154\n at github.com/pingcap/tiup/pkg/cluster/executor.(*CheckPointExecutor).Execute()\n\t
github.com/pingcap/tiup/pkg/cluster/executor/checkpoint.go:85 at 
github.com/pingcap/tiup/pkg/cluster/task.(*Mkdir).Execute()\n\t
github.com/pingcap/tiup/pkg/cluster/task/mkdir.go:61\n at 
github.com/pingcap/tiup/pkg/cluster/task.(*Serial).Execute()\n\t
github.com/pingcap/tiup/pkg/cluster/task/task.go:85\n at 
github.com/pingcap/tiup/pkg/cluster/task.(*StepDisplay).Execute()\n\t
github.com/pingcap/tiup/pkg/cluster/task/step.go:87\n at 
github.com/pingcap/tiup/pkg/cluster/task.(*Parallel).Execute.func1()\n\t
github.com/pingcap/tiup/pkg/cluster/task/task.go:134\n at runtime.goexit()\n\truntime/asm_amd64.s:1371\n
github.com/pingcap/errors.AddStack\n\tgithub.com/pingcap/errors@v0.11.4/errors.go:174\n
github.com/pingcap/errors.Trace\n\tgithub.com/pingcap/errors@v0.11.4/juju_adaptor.go:15\n
github.com/pingcap/tiup/pkg/cluster/task.(*Mkdir).Execute\n\t
github.com/pingcap/tiup/pkg/cluster/task/mkdir.go:63\n
github.com/pingcap/tiup/pkg/cluster/task.(*Serial).Execute\n\t
github.com/pingcap/tiup/pkg/cluster/task/task.go:85\n
github.com/pingcap/tiup/pkg/cluster/task.(*StepDisplay).Execute\n\t
github.com/pingcap/tiup/pkg/cluster/task/step.go:87\n
github.com/pingcap/tiup/pkg/cluster/task.(*Parallel).Execute.func1\n\t
github.com/pingcap/tiup/pkg/cluster/task/task.go:134\nruntime.goexit\n\truntime/asm_amd64.s:1371"}
  1. What version of TiUP are you using (tiup --version)?
1.5.1 tiup
Go Version: go1.16.5
Git Ref: v1.5.1
GitHash: f00aeb0783f56c0766c39aa765d183a566f8f0d6

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 pkg/cluster/executor/ssh.go around line 154 and the mkdir task at pkg/cluster/task/mkdir.go:61, then reproduce the reported tiup cluster scale-out command on Fedora 33. Compare the SSH authentication failure with the builtin SSH path and verify that scale-out completes successfully with the reported setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
fedora, go
Domain
cli, devops, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.