cockroachdb / cockroachdb/cockroach
roachtest: ssh_problem failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.ssh_problem [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_UpdatePgoProfile/21415558?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_UpdatePgoProfile/21415558?buildTab=artifacts#/tpcc-nowait/literal/w=1000/nodes=5/cpu=16) on master @ [b2fdb000dc205ced01163bb650fc72c91856c5cf](https://github.com/cockroachdb/cockroach/commits/b2fdb000dc205ced01163bb650fc72c91856c5cf):
Failed with:
```
test tpcc-nowait/literal/w=1000/nodes=5/cpu=16 failed: (tpcc.go:2588).setupPrometheusForRoachtest: unable to push prometheus config: syncedCluster.PutString: put "/tmp/prometheus.yml1013105373" failed: TRANSIENT_ERROR(ssh_problem): ~ scp -r -C -o StrictHostKeyChecking=no -o ConnectTimeout=10 -R -A -i /home/roach/.ssh/id_rsa /tmp/prometheus.yml1013105373 ubuntu@35.185.67.251:/tmp/prometheus/prometheus.yml
ssh: connect to host 35.185.67.251 port 22: Connection timed out
scp: Connection closed
: exit status 255
test artifacts and logs in: /artifacts/tpcc-nowait/literal/w=1000/nodes=5/cpu=16/run_15
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21415558-1783534384-21-n6cpu16-0001 | 34.23.35.190 | 10.142.0.167 |
| teamcity-21415558-1783534384-21-n6cpu16-0002 | 35.196.72.247 | 10.142.0.40 |
| teamcity-21415558-1783534384-21-n6cpu16-0003 | 35.227.10.174 | 10.142.0.27 |
| teamcity-21415558-1783534384-21-n6cpu16-0004 | 34.24.49.165 | 10.142.0.6 |
| teamcity-21415558-1783534384-21-n6cpu16-0005 | 34.23.204.102 | 10.142.0.57 |
| teamcity-21415558-1783534384-21-n6cpu16-0006 | 35.185.67.251 | 10.142.0.47 |
Parameters:
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=16
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=true
- runtimeAssertionsBuild=false
Help
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21415558/tpcc-nowait-literal-w-1000-nodes-5-cpu-16/1783535341808/1783535616934)
See: [Datadog Logs](https://us5.datadoghq.com/logs?query=service%3Aroachtest+%40cluster%3Ateamcity-21415558-1783534384-21-n6cpu16&from_ts=1783535341808&to_ts=1783535616934&live=false&storage=flex_tier)
Same failure on other branches
- #171649 roachtest: ssh_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2.20-rc]
- #171630 roachtest: ssh_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-26.1.6-rc]
- #171625 roachtest: ssh_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.4.12-rc]
- #171529 roachtest: ssh_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.1.30-rc]
- #170436 roachtest: ssh_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-26.1.5-rc]
- #170428 roachtest: ssh_problem failed [O-roachtest O-robot O-rsg T-testeng X-infra-flake branch-release-25.4.11-rc]
- #170380 roachtest: ssh_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2.19-rc]
/cc @cockroachlabs/test-eng
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*ssh_problem.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-65597
Contributor guide
Research direction
Start with pkg/cmd/roachtest/README.md and the tpcc.go:2588 setupPrometheusForRoachtest entry point, then inspect the linked TeamCity artifacts and logs for the ssh_problem timeout. Compare the repeated failures listed in this issue; done means the recurring failure has an identified and validated resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go
- Domain
- infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100