cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#153,247 156 comments 0 reactions 0 assignees View on GitHub
branch-release-25.3 O-roachtest O-robot O-rsg 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/20447020?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20447020?buildTab=artifacts#/unoptimized-query-oracle/disable-rules=half/rand-multi-region) on release-25.3 @ [1fc47a91e51f0eeff9a1eaf86ffc090d0fef9de1](https://github.com/cockroachdb/cockroach/commits/1fc47a91e51f0eeff9a1eaf86ffc090d0fef9de1):

```
test unoptimized-query-oracle/disable-rules=half/rand-multi-region failed: (test_runner.go:850).func4: in provider: ibm: unable to import SSH key in region ca-tor: creating this SSH key will put user over quota. Allocated: 201, Quota: 200 [owner=test-eng]
```

Parameters:
- cloud=ibm
- coverageBuild=false
- cpu=4
- 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-54302

Contributor guide

Open the contributing guide

Research direction

Start with pkg/cmd/roachtest/test_runner.go at line 850 and the roachtest README to understand how cluster creation reports provider failures. Review the linked TeamCity log and artifacts for the IBM SSH-key quota failure; the issue does not define a fix or acceptance criteria, so completion would need to be established with test-eng or Jira CRDB-54302.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.