cockroachdb / cockroachdb/cockroach
roachtest: cluster_creation failed
- 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/21260484?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/21260484?buildTab=artifacts#/hibernate-spatial) on release-26.1 @ [95a4771368c0790a26239cb6be532865c8227967](https://github.com/cockroachdb/cockroach/commits/95a4771368c0790a26239cb6be532865c8227967):
```
test hibernate-spatial failed: (test_runner.go:991).func4: in provider: ibm: failed to create instance teamcity-21260484-1773722414-334-n1cpu4-0001 in region ca-tor: failed to create instance teamcity-21260484-1773722414-334-n1cpu4-0001 in region ca-tor: user does not have access to selected profile [owner=test-eng]
```
Parameters:
- cloud=ibm
- coverageBuild=false
- cpu=4
- 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 @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-61638
Contributor guide
Research direction
Start with the roachtest guidance in pkg/cmd/roachtest/README.md and review the linked cluster_creation failure artifacts. Investigate the IBM provider failure for the hibernate-spatial test in region ca-tor and the selected profile access. Done means the cluster_creation run can create the instance and complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100