cockroachdb / cockroachdb/cockroach
roachtest: dns_problem failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.dns_problem [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/14532428?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/14532428?buildTab=artifacts#/acceptance/cli/node-status) on master @ [c994982a8be5af89f594e115e897dd6d62cf99d8](https://github.com/cockroachdb/cockroach/commits/c994982a8be5af89f594e115e897dd6d62cf99d8):
```
test acceptance/cli/node-status failed: (cluster.go:2229).Start: in provider: gce: output: ERROR: (gcloud.dns.record-sets.create) HTTPError 409: The resource 'entity.rrset' named '_system-sql._tcp.teamcity-14532428-1711258209-02-n4cpu4.roachprod-managed.crdb.io. (SRV)' already exists: exit status 1
test artifacts and logs in: /artifacts/acceptance/cli/node-status/run_1
```
Parameters:
- ROACHTEST_arch=amd64
- ROACHTEST_cloud=gce
- ROACHTEST_coverageBuild=false
- ROACHTEST_cpu=4
- ROACHTEST_encrypted=false
- ROACHTEST_fs=ext4
- ROACHTEST_localSSD=true
- ROACHTEST_metamorphicBuild=false
- ROACHTEST_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)
See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-14532428/acceptance-cli-node-status/1711258696009/1711258896955)
/cc @cockroachdb/test-eng
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*dns_problem.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Jira issue: CRDB-36968
Contributor guide
Research direction
Start with pkg/cmd/roachtest/README.md, the acceptance/cli/node-status artifacts, and the failure at cluster.go:2229. Inspect the TeamCity log and Grafana link to determine why the GCE DNS SRV record already exists. Done means the dns_problem failure is understood and the test no longer fails from this duplicate-record error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go
- Domain
- cloud, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100