cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#158,857 1178 comments 0 reactions 0 assignees View on GitHub
branch-master O-roachtest O-robot T-testeng X-infra-flake
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

roachtest.cluster_creation [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20815619?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20815619?buildTab=artifacts#/tpccbench/nodes=3/cpu=16/write-optimization=pipelining) on master @ [a76eb5de5d3fdeb4f1276eefe5fdb11e6ebe53a4](https://github.com/cockroachdb/cockroach/commits/a76eb5de5d3fdeb4f1276eefe5fdb11e6ebe53a4):

```
test tpccbench/nodes=3/cpu=16/write-optimization=pipelining failed: (test_runner.go:990).func4: in provider: ibm: failed to configure IBM Cloud account: failed to get or create transit gateway: failed to get transit gateways: Internal Server Error [owner=test-eng]
```

Parameters:
- cloud=ibm
- coverageBuild=false
- cpu=16
- runtimeAssertionsBuild=false
- ssd=0
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)

/cc @cockroachdb/test-eng

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cluster_creation.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-57526

Contributor guide

Open the contributing guide

Research direction

Start with the linked TeamCity log and artifacts, then read the roachtest README and the linked internal investigation guide. Trace the IBM Cloud setup failure through the reported transit-gateway error and review the issue discussion for prior findings. Done means the cause is identified, the failure is addressed or clearly classified as external, and the cluster_creation test passes on rerun.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, infrastructure, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.