cockroachdb / cockroachdb/cockroach
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_RoachtestNightlyGceBazel/20597450?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/20597450?buildTab=artifacts#/jepsen/sequential/start-stop-2) on release-24.1.25-rc @ [fc938cc8bc2ed39db52fb0fbc6fdda3774827e33](https://github.com/cockroachdb/cockroach/commits/fc938cc8bc2ed39db52fb0fbc6fdda3774827e33):
```
test jepsen/sequential/start-stop-2 failed: (cluster.go:2392).Run: full command output in run_094934.108790758_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/sequential/start-stop-2/run_1
```
Parameters:
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=4
- encrypted=false
- fs=ext4
- localSSD=true
- 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)
See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-20597450/jepsen-sequential-start-stop-2/1760435368788/1760436909776)
Same failure on other branches
- #155355 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.3.3-rc]
- #154330 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.4]
- #153255 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2.6-rc]
- #153254 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.3.2-rc]
- #153251 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.1.24-rc]
- #153250 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.3]
- #148075 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2]
- #147485 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-25.2.1-rc]
- #147484 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.1.19-rc]
- #147482 roachtest: apt_problem failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-24.3.14-rc]
/cc @cockroachdb/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-55404
Contributor guide
Research direction
Start with the run_094934.108790758_n1-6_sh-c-sudo-DEBIANFRON.log artifact and the roachtest README, then compare the repeated apt_problem reports linked in the issue. Done means identifying the recurring cause of the exit status 100 failure and documenting or implementing a verified remediation for the affected roachtest runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100