cockroachdb / cockroachdb/cockroach
roachtest: cluster_creation failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
**Note:** This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.
roachtest.cluster_creation [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAzureBazel/20651564?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAzureBazel/20651564?buildTab=artifacts#/jepsen/bank-multitable/subcritical-skews) on master @ [901677f2dee53449e53708ff0aa318d8ee235c02](https://github.com/cockroachdb/cockroach/commits/901677f2dee53449e53708ff0aa318d8ee235c02):
```
test jepsen/bank-multitable/subcritical-skews failed: (test_runner.go:990).func4: in provider: azure: unable to authenticate; please use ``az login`` or double check environment variables [owner=test-eng]
```
Parameters:
- cloud=azure
- coverageBuild=false
- cpu=4
- runtimeAssertionsBuild=true
- 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-55810
Contributor guide
Research direction
Start with the roachtest README, then inspect the linked TeamCity log and artifacts for roachtest.cluster_creation on Azure. Determine whether the authentication failure is reproducible and what follow-up is needed; done means the test passes or the failure has a concrete, actionable report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, 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