cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#173,219 264 comments 0 reactions 0 assignees View on GitHub
branch-release-25.2.23-rc 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_RoachtestNightlyAwsBazel/21457724?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/21457724?buildTab=artifacts#/admission-control/disk-bandwidth-limiter) on release-25.2.23-rc @ [47963926a5d710331e613d38fb40d15828ce18ac](https://github.com/cockroachdb/cockroach/commits/47963926a5d710331e613d38fb40d15828ce18ac):

```
test admission-control/disk-bandwidth-limiter failed: (test_runner.go:840).func4: in provider: aws: failed to run: aws ec2 run-instances --associate-public-ip-address --count 1 --instance-type m6id.2xlarge --image-id ami-0e83be366243f524a --key-name teamcity-runner-w4I_lFaPrndL3RGEbTbnR8-xTkA= --region us-east-2 --security-group-ids sg-04d72b57e29d671f1 --subnet-id subnet-0258dc9d1b6473d84 --tag-specifications ResourceType=instance,Tags=[{Key=usage,Value=roachtest},{Key=roachtest-branch,Value=release-25-2-23-rc},{Key=Cluster,Value=teamcity-21457724-1786252121-05-n2cpu8},{Key=spot,Value=true},{Key=roachprod,Value=true},{Key=cluster,Value=teamcity-21457724-1786252121-05-n2cpu8},{Key=lifetime,Value=12h0m0s},{Key=arch,Value=amd64},{Key=created,Value=2026-08-09T05:12:47Z},{Key=Name,Value=teamcity-21457724-1786252121-05-n2cpu8-0001}] ResourceType=volume,Tags=[{Key=usage,Value=roachtest},{Key=roachtest-branch,Value=release-25-2-23-rc},{Key=Cluster,Value=teamcity-21457724-1786252121-05-n2cpu8},{Key=spot,Value=true},{Key=roachprod,Value=true},{Key=cluster,Value=teamcity-21457724-1786252121-05-n2cpu8},{Key=lifetime,Value=12h0m0s},{Key=arch,Value=amd64},{Key=created,Value=2026-08-09T05:12:47Z},{Key=Name,Value=teamcity-21457724-1786252121-05-n2cpu8-0001}] --user-data file:///tmp/aws-startup-script1576801677 --iam-instance-profile Name=roachprod-testing --block-device-mapping file:///tmp/aws-block-device-mapping1675648534 --instance-market-options MarketType=spot,SpotOptions={SpotInstanceType=one-time,InstanceInterruptionBehavior=terminate} --output json: stderr:
An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 2): We currently do not have sufficient m6id.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get m6id.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c.: exit status 254 [owner=test-eng]
```

Parameters:
- MetamorphicFilesystem=ext4
- MetamorphicVolumeType=local-ssd
- cloud=aws
- coverageBuild=false
- cpu=8
- diskCount=0
- 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)

/cc @cockroachlabs/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)

Contributor guide

Open the contributing guide

Research direction

Start with the linked TeamCity build log and artifacts, then read the roachtest README and inspect the cluster_creation report for the admission-control/disk-bandwidth-limiter failure. Compare the roachdash history and AWS capacity error to determine the expected handling; done means the test can create its cluster reliably or the infrastructure failure is clearly addressed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.