cockroachdb / cockroachdb/cockroach
roachtest: apt_problem failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.apt_problem [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/21425746?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/21425746?buildTab=artifacts#/jepsen/bank/majority-ring-start-kill-2) on release-26.1.8-rc @ [e3abeca7ec25cee7ec1962e9dc33131f74eaf950](https://github.com/cockroachdb/cockroach/commits/e3abeca7ec25cee7ec1962e9dc33131f74eaf950):
Failed with:
```
test jepsen/bank/majority-ring-start-kill-2 failed: (cluster.go:2687).Run: full command output in run_084337.227091578_n1-6_sh-c-sudo-DEBIANFRON.log: error persisted after 3 attempts: TRANSIENT_ERROR(apt_problem): exit status 100
test artifacts and logs in: /artifacts/jepsen/bank/majority-ring-start-kill-2/cpu_arch=arm64/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21425746-1784178569-107-n6cpu4-0001 | 35.231.166.219 | 10.142.5.180 |
| teamcity-21425746-1784178569-107-n6cpu4-0002 | 34.73.147.49 | 10.142.0.71 |
| teamcity-21425746-1784178569-107-n6cpu4-0003 | 35.231.219.191 | 10.142.3.209 |
| teamcity-21425746-1784178569-107-n6cpu4-0004 | 34.24.129.229 | 10.142.2.255 |
| teamcity-21425746-1784178569-107-n6cpu4-0005 | 35.196.147.157 | 10.142.4.199 |
| teamcity-21425746-1784178569-107-n6cpu4-0006 | 35.237.224.149 | 10.142.1.50 |
Parameters:
- arch=arm64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=true
- metamorphicLeases=default
- 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-21425746/jepsen-bank-majority-ring-start-kill-2/1784191328928/1784191730309)
Same failure on other branches
- #172511 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2.22-rc]
- #171651 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.4.12-rc]
- #171285 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-26.1.5-rc]
- #170470 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2.19-rc]
- #170453 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.4.11-rc]
- #169609 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.4.10-rc]
- #168956 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-26.1.4-rc]
/cc @cockroachlabs/test-eng
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*apt_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-65849
Contributor guide
Research direction
Start with the failed run log run_084337.227091578_n1-6_sh-c-sudo-DEBIANFRON.log and the artifacts under /artifacts/jepsen/bank/majority-ring-start-kill-2/cpu_arch=arm64/run_1. Read the roachtest README and compare the related apt_problem issues on other branches. Done means identifying the recurring cause and addressing the failure so the affected roachtest configuration no longer reports apt_problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, gcp, go
- Domain
- cloud, infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100