roachtest: failover/chaos/read-only failed #107865
Description
roachtest.failover/chaos/read-only failed with artifacts on release-23.1 @ 8b970683af4630cbb30b4c92f0be86cfadd97993:
(cluster.go:2249).Run: output in run_124106.058283365_n1-10_echo-0-sudo-blockdev: echo "0 $(sudo blockdev --getsz /dev/sdb) linear /dev/sdb 0" | sudo dmsetup create data1 returned: COMMAND_PROBLEM: exit status 1
(cluster.go:2249).Run: cluster.RunE: context canceled
(cluster.go:2249).Run: cluster.RunE: context canceled
(cluster.go:2249).Run: cluster.RunE: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-only/run_1
Parameters: ROACHTEST_arch=amd64
, ROACHTEST_cloud=gce
, ROACHTEST_cpu=2
, ROACHTEST_encrypted=false
, ROACHTEST_fs=ext4
, ROACHTEST_localSSD=false
, ROACHTEST_ssd=0
This test on roachdash | Improve this report!
Jira issue: CRDB-30230
Metadata
Metadata
Assignees
Labels
Testing tools and infrastructureCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Broken test (automatically or manually discovered).Originated from a bot.TestEng Teamthe automatically generated issue was closed due to an infrastructure problem not a product issueUsed to mark GA and release blockers, technical advisories, and bugs for 23.1