cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#156,211 15 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

**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/20652610?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAzureBazel/20652610?buildTab=artifacts#/process-lock) on master @ [cdcf76d0af53d78418ed10585fca7987c1c0aedc](https://github.com/cockroachdb/cockroach/commits/cdcf76d0af53d78418ed10585fca7987c1c0aedc):

```
test process-lock 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-55857

Contributor guide

Open the contributing guide

Research direction

Start with pkg/cmd/roachtest/README.md and the test_runner.go:990 failure path for the process-lock test. Inspect the cluster_creation run with cloud=azure and its artifacts to determine whether the failure is specific to the test environment or Azure authentication. Done means the cause is confirmed and the roachtest no longer reports this authentication failure, or the environment requirement is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go
Domain
cloud, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.