cockroachdb / cockroachdb/cockroach
basalt-26.3: roachtest: apt_problem 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.apt_problem [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_GreenRoachtestNightlyGcePrivateBasaltBazel/21503773?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_GreenRoachtestNightlyGcePrivateBasaltBazel/21503773?buildTab=artifacts#/jepsen/sets/parts-start-kill-2) on basalt-26.3 @ [017b84cd0101b832a6ee0c1934d073d108d0b24a](https://github.com/cockroachdb/cockroach/commits/017b84cd0101b832a6ee0c1934d073d108d0b24a):
Failed with:
```
test jepsen/sets/parts-start-kill-2 failed: (cluster.go:4353).Run: full command output in run_130141.814929317_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/sets/parts-start-kill-2/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21503773-1788847911-262-n6cpu4-0001 | | 10.91.96.114 |
| teamcity-21503773-1788847911-262-n6cpu4-0002 | | 10.91.96.6 |
| teamcity-21503773-1788847911-262-n6cpu4-0003 | | 10.91.100.123 |
| teamcity-21503773-1788847911-262-n6cpu4-0004 | | 10.91.96.140 |
| teamcity-21503773-1788847911-262-n6cpu4-0005 | | 10.91.96.106 |
| teamcity-21503773-1788847911-262-n6cpu4-0006 | | 10.91.100.76 |
Parameters:
- MetamorphicBasaltMultiAZ=true
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=true
- metamorphicLeases=default
- runtimeAssertionsBuild=true
- storageNodesVersion=v0.1.18-nightly.20260907
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-21503773/jepsen-sets-parts-start-kill-2/1788872476709/1788874137173)
_Logs were not uploaded to Datadog_
/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)
Contributor guide
Research direction
Read pkg/cmd/roachtest/README.md, then inspect the full command output in run_130141.814929317_n1-6_sh-c-sudo-DEBIANFRON.log and the artifacts under /artifacts/jepsen/sets/parts-start-kill-2/run_1. Start at cluster.go:4353 and trace the apt_problem retry failure in parts-start-kill-2. Done means the underlying cause is addressed and the roachtest completes without apt_problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, go
- Domain
- devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100