cockroachdb / cockroachdb/cockroach

release-26.2: roachtest: dns_problem failed

Open
#174,153 2 comments 0 reactions 0 assignees View on GitHub
branch-release-26.2 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.dns_problem [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21487511?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21487511?buildTab=artifacts#/process-lock) on release-26.2 @ [a7968b31196218f719804a2e841ae3fd2964ff29](https://github.com/cockroachdb/cockroach/commits/a7968b31196218f719804a2e841ae3fd2964ff29):

Failed with:

```
test process-lock failed: (test_monitor.go:35).func1: test monitor: EOF [owner=test-eng]
(cluster.go:2692).Start: TRANSIENT_ERROR(dns_problem): output: : signal: killed
test artifacts and logs in: /artifacts/process-lock/cpu_arch=arm64/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21487511-1787812444-243-n4cpu4-0001 | | 10.91.97.65 |
| teamcity-21487511-1787812444-243-n4cpu4-0002 | | 10.91.98.242 |
| teamcity-21487511-1787812444-243-n4cpu4-0003 | | 10.91.98.243 |
| teamcity-21487511-1787812444-243-n4cpu4-0004 | | 10.91.96.219 |

Parameters:
- arch=arm64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=true
- fs=ext4
- localSSD=true
- metamorphicLeases=leader
- 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)

See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21487511/process-lock/1787842350345/1787842729871)

Same failure on other branches

- #171906 release-26.3: roachtest: dns_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-26.3]
- #137246 roachtest: dns_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.2]
- #125300 roachtest: dns_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.1]
- #121092 roachtest: dns_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-23.1]
- #121090 roachtest: dns_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-23.2]
- #120959 roachtest: dns_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-master]

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

Contributor guide

Open the contributing guide

Research direction

Start with the roachtest README and the dns_problem failure artifacts under /artifacts/process-lock/cpu_arch=arm64/run_1. Review the linked TeamCity logs and Grafana view to determine why process-lock is killed during cluster startup. Done means identifying and correcting the failure so dns_problem passes reliably on the affected configuration.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.