Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

roachtest: failover/chaos/read-only failed #126660

Closed
cockroach-teamcity opened this issue Jul 3, 2024 · 4 comments
Closed

roachtest: failover/chaos/read-only failed #126660

cockroach-teamcity opened this issue Jul 3, 2024 · 4 comments
Assignees
@itsbilal
Labels
A-testing Testing tools and infrastructure branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-3 Issues/test failures with no fix SLA T-storage Storage Team
Projects
KV
Milestone
23.2

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jul 3, 2024 •
edited by cockroach-jira-scripts
Loading

roachtest.failover/chaos/read-only failed with artifacts on release-23.2 @ ea13ed571d241e9021ffdc523ee73021b399356c:

(disk_stall.go:312).Setup: full command output in run_135336.902727053_n1-10_echo-0-sudo-blockdev.log: COMMAND_PROBLEM: exit status 1
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-only/cpu_arch=arm64/run_1

Parameters:

  • ROACHTEST_arch=arm64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=2
  • ROACHTEST_encrypted=false
  • ROACHTEST_fs=ext4
  • ROACHTEST_localSSD=false
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-40044
@cockroach-teamcity cockroach-teamcity added branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-kv KV Team labels Jul 3, 2024
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone Jul 3, 2024
@cockroach-teamcity cockroach-teamcity added this to roachtest/unit test backlog in KV Jul 3, 2024
@cockroach-teamcity
Copy link
Member Author

roachtest.failover/chaos/read-only failed with artifacts on release-23.2 @ d09da53496ac01269267a4d7d539ba6c840bbdb7:

(disk_stall.go:312).Setup: full command output in run_135932.961774290_n1-10_echo-0-sudo-blockdev.log: COMMAND_PROBLEM: exit status 1
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
(cluster.go:2344).Run: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-only/cpu_arch=arm64/run_1

Parameters:

  • ROACHTEST_arch=arm64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=2
  • ROACHTEST_encrypted=false
  • ROACHTEST_fs=ext4
  • ROACHTEST_localSSD=false
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

This test on roachdash | Improve this report!

@kvoli
Copy link
Collaborator

kvoli commented Jul 8, 2024

It looks like we are also seeing this failure on 23.2, could you take a look when you get a chance @andrewbaptist?

from:

Closing as this is on 23.1. This was fixed on the 23.2+ releases.

@kvoli kvoli added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-testing Testing tools and infrastructure P-3 Issues/test failures with no fix SLA and removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Jul 8, 2024
@andrewbaptist andrewbaptist added the T-storage Storage Team label Jul 8, 2024
@blathers-crl blathers-crl bot added the A-storage Relating to our storage engine (Pebble) on-disk storage. label Jul 8, 2024
@andrewbaptist andrewbaptist removed A-storage Relating to our storage engine (Pebble) on-disk storage. T-kv KV Team labels Jul 8, 2024
@andrewbaptist
Copy link
Collaborator

This is an issue with the storage block device, but I thought it was fixed on 23.2. @itsbilal can you take a look.

@itsbilal
Copy link
Member

itsbilal commented Jul 9, 2024

This was backported to 23.2 yesterday.

@itsbilal itsbilal closed this as completed Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@itsbilal itsbilal

Labels
A-testing Testing tools and infrastructure branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-3 Issues/test failures with no fix SLA T-storage Storage Team
Projects
KV
roachtest/unit test backlog
Storage
Archived in project
Milestone
23.2
Development

No branches or pull requests
4 participants
@itsbilal @cockroach-teamcity @kvoli @andrewbaptist